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

CursorManager no longer needs to handle ClientCursor::dispose() outside of mutexes

    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • Storage Execution
    • Execution Team 2022-09-05

    Description

      I believe disposal of client cursors no longer require a collection-level lock. The deadlock concern dates back to when there were cursor managers per collection, which is no longer the case: we have a global cursor manager with its own internal concurrency control.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: