-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Minor Change
-
ALL
... which leads to connections being broken unnecessarily.
One such case - if a majority of members are unchanged and the primary is one of the unchanged members. Ex: one secondary node out of a three-node replica set goes bad and we want to replace it with another good node. If that node being down doesn't require a stepdown, then the node changing shouldn't either?
- depends on
-
SERVER-15160 TopologyCoordinatorImpl should not always step down on reconfig
- Closed
- is duplicated by
-
SERVER-6752 Do not close all connections on replica set reconfig
- Closed
-
SERVER-7833 mongos need restart after rs.remove
- Closed