-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10
-
140
Retrying the setAllowMigrations command with a session and a txnNum (retryableWrite:true) may end up with a deadlock, competing for a session checkout and the _kChunkOpLock acquisition, as it's shown below:
First cmd: session checkout > lock _kChunkOpLock > session check-in > transaction happens > session checkout > unlock _kChunkOpLock
Second cmd: session checkout > lock _kChunkOpLock > session check-in > transaction happens > session checkout > unlock _kChunkOpLock
- is related to
-
SERVER-73539 stopMigrations/resumeMigrations don't have replay protection
- Closed
- related to
-
SERVER-79026 Failing to cancel the JournalFlusher thread might lead to 3-way deadlock
- Closed