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

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

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Execution Team 2022-09-05

      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.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: