If a node is stepping down in multiple threads at once, one thread can lag behind the other stepdown thread and still be running when the node starts applying oplog entries as a secondary. In this case, if the remaining stepdown thread still has ScopedBlockSessionCheckouts in scope, it will block checking out sessions, which could cause us to fail to apply a commitTransaction oplog entry, ultimately triggering this fassert.
- depends on
-
SERVER-58143 shardsvrDropCollectionParticipant should be killable on stepdown
- Closed
- is caused by
-
SERVER-52564 Deadlock between step down and MongoDOperationContextSession
- Closed
- is duplicated by
-
SERVER-57545 Stepping down while stepping up with a transaction prepared results in a broken node
- Closed
- is related to
-
SERVER-55007 Deadlock between step down and MongoDOperationContextSession
- Closed
-
SERVER-55573 Deadlock between stepdown and chunk migration
- Closed
- related to
-
SERVER-59226 Deadlock when stepping down with a profile session marked as uninterruptible
- Closed