Remove unnecessary voting after replica set config change

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Unassigned
              Reporter:
              Juho Mäkinen
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: