-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Minor Change
-
ALL
-
Repl 2017-04-17, Repl 2017-05-08, Repl 2017-05-29, Repl 2017-06-19, Repl 2017-07-31, Repl 2017-08-21, Repl 2017-09-11, Repl 2017-10-02
-
0
Currently the stepdown command runs with the global lock in shared mode, which violates the concurrency rules for the _canAcceptNonLocalWrites variable.
- is depended on by
-
SERVER-27892 Clarify locking rules for _canAcceptNonLocalWrites and _canServeNonLocalReads
- Closed
- is related to
-
SERVER-28702 Race condition of stepdown command and signaling stepdown waiter
- Closed
-
SERVER-30852 Force reconfig that makes current primary unelectable can result in stepdown without taking the global lock
- Closed
- related to
-
SERVER-31223 fix race in StepDownTest::OnlyOneStepDownCmdIsAllowedAtATime
- Closed
-
SERVER-30719 Fix dbCheck behavior during stepdown
- Closed