-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
Catalog and Routing
-
Storage NYC 2019-02-11, Execution Team 2020-01-13
This is follow up work for SERVER-33244, to add a max lock acquisition timeout override (_maxLockTimeout) for transactions in order to prevent transactions from deadlocking with one another.
UninterruptibleLockGuard cannot be used in transaction operation code paths if we wish to prevent deadlocks. However, query currently uses UninterruptibleLockGuard in the find/agg code paths. So this work is blocked on the completion of SERVER-33575, to remove UninterruptibleLockGuard usages from query code paths.
- depends on
-
SERVER-71444 [Sharding] Remove or document instances of UninterruptibleLockGuard
- Open
-
SERVER-33575 Remove UninterruptibleLockGuards in query code to allow interruptible lock acquisition
- Closed
-
SERVER-45608 Remove UninterruptibleLockGuard from TransactionParticipant
- Closed
- related to
-
SERVER-33244 Make all lock acquisitions for transactions have 0 second timeout
- Closed