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

Randomize priority takeover timeout

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.4, 3.5.4
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • v3.4
    • Repl 2017-02-13, Repl 2017-03-06

      We do not apply any random offset to the priority takeover election timeout. This means that if two nodes with the same priority discover that a lower priority primary at about the same time, they have an increased chance of both running for takeover election, both losing, and putting the system back into the "scramble to find any primary" behavior. This might then allow the low-priority node to get re-elected as primary, restarting the process.

            Assignee:
            william.schultz@mongodb.com William Schultz (Inactive)
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: