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

Log diagnostic message when creating "no timeout" cursors

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Querying
    • None
    • Query Execution

    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

        Activity

          People

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

            Dates

              Created:
              Updated: