Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-12689

Improve log message when capped cursor is overrun

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 2.5.5
    • Component/s: Querying
    • None
    • Query

      When a capped cursor is overrun, the following warning is displayed on the server:

      warning: collection dropped during yield of collscan or state deleted
      

      Perhaps it's not worth warning in the case of an overrun, given that this is the nature of a capped collection (and the client can interpret an empty result set with a dead cursor as a possible indicator of this state). If it is worth logging something, it would be helpful to explicitly state why the cursor was invalidated.

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            benjamin.becker Ben Becker
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: