Improve log message when capped cursor is overrun

XMLWordPrintableJSON

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

      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 - Query Team (Inactive)
              Reporter:
              Ben Becker (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: