[SERVER-6845] Configuration changes in a Replica Set do not affect Primary connections: non-primary servers cannot affect primary connections Created: 24/Aug/12  Updated: 03/Mar/15  Resolved: 23/Feb/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.7.8

Type: Improvement Priority: Minor - P4
Reporter: mark nielsen Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Participants:

 Description   

When making configurations changes, such as removing a secondary, it drops connections to the primary. Not sure if sharding affects this or not.

The feature request is no connections to the primary should be affected (other than replica connections) for any changes to the replica set where a majority of servers is up and the primary server stays the primary server.

From a systems administration point of view, when systems go down or need to be replaced in production live, the primary dropping all of its connections is very bad. The changes to the replica set should go unnoticed to the primary.


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