Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v3.6, v3.4
-
Sprint:Repl 2018-05-21
-
Linked BF Score:17
Description
After stepdown, the old primary should store the last vote successfully even if the operation has been killed due to InterruptedDueToReplStateChange. The response should return
{ ok: 1 }.
Attachments
Issue Links
- is caused by
-
SERVER-27534 All writing operations must fail if the term changes
-
- Closed
-
- is related to
-
SERVER-34661 Return early when the vote request response has an error
-
- Closed
-
- related to
-
SERVER-35766 Replication commands sent in candidate's new term can interrupt concurrent vote request
-
- Closed
-
-
SERVER-47612 Elections not robust in remove_newly_added_field_after_finishing_initial_sync.js
-
- Closed
-