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

heartbeat response from secondary should not schedule priority takeover

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0-rc3
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl C (11/20/15)
    • Linked BF Score:
      0

      Description

      The topology coordinator schedules a priority takeover whenever its internal state indicates that the existing primary has a lower priority than the current node and the term of the remote node matches its own.

      When an election is taking place (due to a node with a higher priority than the current) and the current primary is in the midst of stepping down, it will not update its own term due to SERVER-21425. But the term in other nodes would have increased. The heartbeat responses from these secondaries would be sufficient to trigger a priority takeover.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: