stale term stepdown must be atomic

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.2.0-rc3
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl C (11/20/15)
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Eric Milkie
              Reporter:
              Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: