-
Type: Task
-
Resolution: Unresolved
-
Priority: 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.
- depends on
-
SERVER-69059 Create an InterruptibleLockGuard to place in ClientCursorPin to ensure read operations are interruptible
- Closed
- related to
-
SERVER-33959 CursorManager attempts to dispose of aggregation cursors while holding partitioned lock, which leads to deadlock
- Closed
-
SERVER-67424 Seek and destroy open storage cursors saved in the CursorManager across commands on rollback/shutdown (storage engine closure)
- Open