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

.maxTimeMs leaks shard cursor

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • ALL
    • 0

      max_time_ms_does_not_leak_shard_cursor.js fails periodically (3% of evergreen runs), because there is an open cursor on shards after the mongoS query (correctly) failed with MaxTimeMSExpired. The test was added in 6.0 in response to SERVER-62710.

      Possible solution idea: the remaining time is transferred from the cursor to the opCtx. Perhaps, the timeout should be removed from opCtx at the end of getMore.

            Assignee:
            romans.kasperovics@mongodb.com Romans Kasperovics
            Reporter:
            romans.kasperovics@mongodb.com Romans Kasperovics
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: