-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
Since stepdown requires a global shared lock, it will block waiting possibly a very long time if there are long running write operations with a document-level-locking storage engine. Such write operations could be things like map/reduce or index builds. We should kill those operations before attempting to enqueue the global shared lock.
- depends on
-
SERVER-16194 Lock manager should expose methods that separate enqueuing a lock request and waiting for it to be satisfied
- Closed
- related to
-
SERVER-17150 logOp fassert when dropping collection on stepped-down primary
- Closed
-
SERVER-15308 Stepdown does not cancel active (background) index builds causing shutdown on completion
- Closed
-
SERVER-17435 Invariant failure when killing user ops during stepdown
- Closed