Details
-
Improvement
-
Resolution: Gone away
-
Major - P3
-
None
-
None
-
None
-
None
-
Storage Execution
Description
UninterruptibleLockGuard cannot be used in transaction operation code paths if we wish to prevent deadlocks. SERVER-34951 would invariant that UninterruptibleLockGuard is not used along with _maxLockTimeout (which is set for all transactions) in LockerImpl, but is blocked on this ticket.
Specifically, the UninterruptibleLockGuard in commitUnpreparedTransactions should be removed. Other uses of UninterruptibleLockGuard in TransactionParticipant should be investigated as well.
Attachments
Issue Links
- is depended on by
-
SERVER-34951 LockerImpl should invariant against active UninterruptibleLockGuard usage when _maxLockTimeout is set
-
- Backlog
-