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

stale term stepdown must be atomic

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • 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

      Currently, if a primary detects that the term has increased, it schedules a stepdown (and state change) to eventually occur, but it updates its term immediately. This can cause issues, because other things can be scheduled ahead of the stepdown; these things can report to other nodes the new term but with the old primary.

        Attachments

          Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-21452 heartbeat response from secondary should not schedule priority takeover

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: