[SERVER-69143] CursorManager no longer needs to handle ClientCursor::dispose() outside of mutexes Created: 25/Aug/22  Updated: 05/Dec/22

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-69059 Create an InterruptibleLockGuard to p... Closed
Related
related to SERVER-33959 CursorManager attempts to dispose of ... Closed
related to SERVER-67424 Seek and destroy open storage cursors... Open
Assigned Teams:
Storage Execution
Sprint: Execution Team 2022-09-05
Participants:

 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.


Generated at Thu Feb 08 06:12:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.