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

Unwin-able primary takeovers can be scheduled on priority:0 nodes

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
    • Replication
    • Fully Compatible
    • Repl 2023-03-06, Repl 2023-03-20, Repl 2023-04-03

      _shouldTakeOverPrimary doesn't check if a node is priority:0 before scheduling a priority or catchup takeover. Later on, it will choose not to stand for election. This is confusing in the logs and wastes a very tiny amount of resources on the node.

      This can clearly be seen in this test.

            Assignee:
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: