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

Log diagnostic message when creating "no timeout" cursors

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Querying
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated: