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

primary stepdown on reconfig isn't needed in some cases

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Minor Change
    • Operating System:
      ALL

      Description

      ... 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?

        Attachments

          Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-15160 TopologyCoordinatorImpl should not always step down on reconfig

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-6752 Do not close all connections on replica set reconfig

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-7833 mongos need restart after rs.remove

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              spencer Spencer Brody
              Reporter:
              greg_10gen Greg Studer
              Participants:
              Votes:
              9 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: