-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
Fully Compatible
-
ALL
-
v5.0
-
Sharding 2021-07-12
-
127
Killing an opCtx triggers the execution of tasks scheduled on its baton (see here). Some of those tasks may acquire locks, and this acquisition could violate the hierarchical lock acquisition invariants in the context of SessionCatalog.
Currently, the SessionCatalog kills operations (here) while holding a level 0 mutex (here). This ticket should change this behavior and have the operation killed without holding the SessionCatalog mutex.