TopologyCoordinatorImpl should not always step down on reconfig

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.7.8
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Minor Change
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Spencer Brody (Inactive)
              Reporter:
              Andy Schwerin
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: