-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.7.9
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2018-05-07, Repl 2018-05-21
This will help prevent killSessions from blocking on locks held by a transaction it plans to kill.
A suggested ordering for session kill is:
- Kill transactions
- Kill operations
- Kill cursors
- is duplicated by
-
SERVER-34707 Write JS test for transactions on sessions that get killed concurrently
- Closed
- is related to
-
SERVER-34732 collection drop hangs in test of transactions
- Closed
- related to
-
SERVER-34781 Abandoned cursor in a transaction can block other operations
- Closed
-
SERVER-35217 killSessions command attempts to kill a transaction while holding SessionCatalog::_mutex, which leads to deadlock
- Closed