Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Sprint:
Execution Team 2022-09-05
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: [DO NOT USE] Backlog - Storage Execution Team
Reporter:: Dianna Hohensee (Inactive)
Participants:: [DO NOT USE] Backlog - Storage Execution Team, Dianna Hohensee
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Aug 25 2022 04:33:53 PM UTC
Updated:: Dec 05 2022 11:48:23 PM UTC
Confidence Status Last Update:: 25/Aug/22 5:09 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates