-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.0.2, 2.2.0-rc0
-
Component/s: Replication
-
Environment:Ubuntu 10.04.3 LTS
-
Linux
cluster of 3 nodes and clients connected through mongos
from primary issue rs.remove("secondary1")
found application lost connection and threw error lost connection to primary node.
This consistently happens even when the cluster is 4-node or 5-node.
- duplicates
-
SERVER-5788 primary stepdown on reconfig isn't needed in some cases
- Closed
- is duplicated by
-
SERVER-9717 Remove unnecessary voting after replica set config change
- Closed
- related to
-
SERVER-5286 DBClientBase::findN: transport error for query: { mapreduce.shardedfinish: {....} }
- Closed
-
SERVER-4315 Make sure replica set primary does not disconnect unnecessarily on reconfig
- Closed
-
SERVER-6376 Tag replica set nodes without election or reconnections
- Closed