Allow priority takeover without direct heartbeats from the current primary

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      From siyuan.zhou@mongodb.com in SERVER-21452:
      Given that priority takeover is based on heartbeats, if the secondary with higher priority cannot connect to the existing primary, it will never take over the primary, like in the following case.

      P(priority: 2) <-> S(priority: 1) <-> S(priority: 3)

      And this is not ideal.

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Lingzhi Deng
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: