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

TopologyCoordinatorImpl should not always step down on reconfig

    XMLWordPrintable

    Details

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

      Description

      The heartbeating implementation in TopologyCoordinatorImpl does not attempt to stay primary across reconfigs where new elections could be avoided. It should, to be consistent with old behavior and to minimize the number of unnecessary elections.

        Attachments

          Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-5788 primary stepdown on reconfig isn't needed in some cases

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-11564 replset reconfigs trigger elections sometimes in some cases in which they shouldn't

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

          Bug - A problem which impairs or prevents the functions of the product. DOCS-10235 Comment on: "manual/tutorial/remove-replica-set-member.txt"

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

            Activity

              People

              Assignee:
              spencer Spencer Brody
              Reporter:
              schwerin Andy Schwerin
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: