Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-5788

primary stepdown on reconfig isn't needed in some cases

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Minor Change
    • ALL

      ... which leads to connections being broken unnecessarily.

      One such case - if a majority of members are unchanged and the primary is one of the unchanged members. Ex: one secondary node out of a three-node replica set goes bad and we want to replace it with another good node. If that node being down doesn't require a stepdown, then the node changing shouldn't either?

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            greg_10gen Greg Studer
            Votes:
            9 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: