[SERVER-6752] Do not close all connections on replica set reconfig Created: 10/Aug/12  Updated: 14/Aug/14  Resolved: 14/Aug/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.0.2, 2.2.0-rc0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Gopi Assignee: Unassigned
Resolution: Duplicate Votes: 3
Labels: elections
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 10.04.3 LTS


Issue Links:
Duplicate
duplicates SERVER-5788 primary stepdown on reconfig isn't ne... Closed
is duplicated by SERVER-9717 Remove unnecessary voting after repli... Closed
Related
related to SERVER-5286 DBClientBase::findN: transport error ... Closed
related to SERVER-4315 Make sure replica set primary does no... Closed
related to SERVER-6376 Tag replica set nodes without electio... Closed
Operating System: Linux
Participants:

 Description   

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.



 Comments   
Comment by Daniel Pasette (Inactive) [ 30/Aug/13 ]

garo, we're working on this issue in SERVER-6376 with intention to prevent dropping connections in all cases where it is possible – in certain cases it's unavoidable (where the primary may be caused to change or a node's visibility may change). Watch that ticket as we'll update as it progresses.

Comment by Juho Mäkinen [ 29/Aug/13 ]

Still hoping that this would resolved in the future. Having the cluster dropping primary when it's not really needed gives the DBA and ops team unnecessary problems and downtime when maintaining the cluster.

Comment by Spencer Brody (Inactive) [ 13/Aug/12 ]

We will still probably want to close all connections on the removed node, but we shouldn't need to close them on the primary or secondaries that didn't have their config changed.

Comment by Spencer Brody (Inactive) [ 13/Aug/12 ]

Yes, this was by design to be overly cautious when we first implemented Replica Sets, but you're right, this is probably unnecessary now and could be removed.

Generated at Thu Feb 08 03:12:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.