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

Log diagnostic message when creating "no timeout" cursors

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • Labels:
      None
    • Query Execution

      As a follow-on from SERVER-19981, it would be very useful when trying to track down an unknown source of noTimeout cursors if queries that produced them were logged at the default level.

      That is, in addition to the millis > slowms logic at logLevel 0, queries that have QueryOption_NoCursorTimeout set and produce a cursor (ie. not exhausted by the first batch and ntoreturn >= 0), should also be logged by default.

            Assignee:
            backlog-query-execution Backlog - Query Execution
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            2 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:

                Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.