-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:None
-
Fully Compatible
-
ALL
-
v4.2, v4.0
-
Repl 2018-10-22, Repl 2018-11-05, Repl 2019-09-23, Repl 2019-11-18, Execution Team 2019-12-16, Repl 2019-12-02, Repl 2019-12-16, Execution Team 2020-01-13, Execution Team 2019-12-30
-
33
The rollback fuzzer suites utilize the RollbackTestFixture to run randomized rollback testing. Some of the suites (e.g. rollback_fuzzer_clean_shutdowns) will shut down nodes at random times. After we shutdown a node, we wait until there is a stable primary so that we can continue doing writes in the test. The way we check this can be racy, though, if we get a current primary that then steps down, and we get that same node as a secondary. Instead of asserting that the primary and secondary are not equal, I think it would be simpler to just check if we shut down the original primary. If so, then we need to wait for a new primary. Otherwise, we shouldn't need to wait, since the original primary should be stable, since it is supported by an arbiter.
- causes
-
SERVER-45400 Reduce OplogFetcher getMore awaitData timeout for nodes in RollbackTest fixture
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-42650 Remove stale comments mentioned in the RollbackTest for "transitionToSteadyStateOperations" state.
-
- Closed
-