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

Delist opCtx during ClientDisconnect during getMores

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v7.0
    • Service Arch 2023-08-21, Service Arch 2023-09-04
    • 120

      checkForInterruptNoAssert calls during handleRequest for getMores that result in ClientDisconnect (being thrown and markKilled) cause an issue where a new killCursor opCtx is created and the old opCtx is not delisted. Find a way to change this if condition for this exact condition, possibly making a more clear distinction between thrown statuses and opCtx killStatus.

      ServiceEntryPointImpl delist logic

            Assignee:
            alex.li@mongodb.com Alex Li
            Reporter:
            alex.li@mongodb.com Alex Li
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: