-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v3.6
-
Repl 2018-02-26, Repl 2018-03-12
-
0
Successful executions of unconditional stepdowns supercede stepdown attempts in response to replSetStepDown, but the execution of the command will not be killed if it wasn't issued by a client. Nodes attempting a priority takeover in pv0 send this command to the primary. A possible solution might be to make TopologyCoordinator::prepareForStepDownAttempt return an error if a stepdown has already completed (in addition to the existing stepdown-in-progress check.)