[SERVER-39939] Avoid taking any lock manager locks in the killCursors code path Created: 04/Mar/19  Updated: 06/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Anton Korshunov Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: query-44-grooming, storch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-40058 AutoStatsTracker's lock acquisition t... Closed
is related to SERVER-35567 Concurrency simultaneous replication ... Closed
Assigned Teams:
Query Execution
Participants:
Linked BF Score: 0

 Description   

In the killCursors code path we acquire a collection lock via AutoStatsTracker which could cause a deadlock (e.g., when there is a parallel DDL task queueing up on taking a Global X lock). Ideally, we'd want to re-design the killCursors code path to avoid any lock manager locks. Once it is done, the test from SERVER-35567 can be re-enabled (note that the test will require some modifications to avoid getting stuck in the killSessions state, see comments to SERVER-35567 for details).


Generated at Thu Feb 08 04:53:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.