Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
Repl C (11/20/15)
-
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
-
SERVER-21452 heartbeat response from secondary should not schedule priority takeover
-
- Closed
-