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

Only auto-cleanup cursors that have been killed

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • 29
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      See discussion on BF-27364 for more details:

      Instead of doing the auto-kill upon unpinning when 
      cursor->cameFromRouter() && interruptStatus == ErrorCodes::MaxTimeMSExpired, could we set a flag on the cursor indicating that it has been killed in killCursor and check that to determine whether we should destruct it immediately in unpin?

       

            Assignee:
            alyssa.clark@mongodb.com Alyssa Clark
            Reporter:
            alyssa.clark@mongodb.com Alyssa Clark
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None