[SERVER-9717] Remove unnecessary voting after replica set config change Created: 17/May/13  Updated: 09/Jul/16  Resolved: 17/May/13

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

Type: Improvement Priority: Minor - P4
Reporter: Juho Mäkinen Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: voting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-6752 Do not close all connections on repli... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

It seems that currently any change for the replica set config with rs.reconfig() will cause a voting and the cluster will be down for a moment. This should be change so that the primary won't drop to secondary unless it's really necessary.

For example I changed one slave from hidden to non hidden and the rs.reconfig() caused the primary to drop into secondary for a few seconds. I see no reason why this is needed, because it adds downtime for no valid reason.


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