-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.4, v4.2
-
Repl 2020-06-15, Repl 2020-06-29
-
18
Using replTest.stepUp in the test always expects the replica set to have a primary before running replSetStepUp cmd for any retries. It's not possible to hold that guarantee if a test run with high electionTimeOutMillis (24 hrs) because the nodes can't start an election by it's own during the test unless it was started by the jstest explicitly using "replSetStepDown" cmd.
Though SERVER-47612 (on master) made storing last vote document during replSetRequestVotes cmd as resilient against concurrent step down, the solution for this ticket should be more generic to handle any replSetStepUp failures. So, we should make the test to use stepUpNoAwaitReplication instead of stepUp method.
- related to
-
SERVER-47612 Elections not robust in remove_newly_added_field_after_finishing_initial_sync.js
- Closed