-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-03-06, Repl 2017-03-27, 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, Repl 2017-10-23
-
0
- depends on
-
SERVER-28544 Stepdown command must take global lock in exclusive mode
- Closed
- is duplicated by
-
SERVER-28103 ReplicationCoordinatorImpl::canAcceptWritesForDatabase() reads _canAcceptNonLocalWrites without proper locking
- Closed
- is related to
-
SERVER-14601 All "not master" errors should use the same error code
- Closed
-
SERVER-30852 Force reconfig that makes current primary unelectable can result in stepdown without taking the global lock
- Closed
-
SERVER-31431 Ensure that all state transitions in or out of PRIMARY or SECONDARY occur with the global X lock held
- Closed
-
SERVER-31432 Remove all callers of canAcceptWritesFor*_UNSAFE and checkCanServeReadsFor_UNSAFE
- Closed
-
SERVER-27914 Verify canAcceptWritesForDatabase() is called while the caller holds the global lock
- Closed
-
SERVER-27911 Merge all stepdown code paths
- Closed
- related to
-
SERVER-27555 ReplicationCoordinatorImpl::_memberState is read without proper locking
- Closed
-
SERVER-28097 add replset test command to wait for primary to accept writes
- Closed