Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Query Execution
Description
There are at least two cases where we can avoid some mutex locks in ClusterCursorManager class:
- ClusterCursorStats::appendAtLeaf() calls ClusterCursorManager::stats() and ClusterCursorManager::cursorsTimedOut(), both of which require a mutex lock. For both methods appendAtLeaf() is the only caller, so we can combine them.
- ClusterCursorManager::killMortalCursorsInactiveSince locks two times, which also can be reduced to just one lock.
Attachments
Issue Links
- is related to
-
SERVER-70256 Fix the race condition in ClusterCursorManager
-
- Closed
-