-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
v4.2, v4.0
-
Repl 2020-01-27
SERVER-37390 made it so that the RollbackTest fixture uses a high election timeout (24 hours) to prevent unplanned state transitions during test execution. This has the unintended side effect of slowing down tests that use this fixture since the awaitData timeout on getMores sent by the OplogFetcher are affected by the election timeout. A 24 hour election timeout causes us to use the maximum awaitData timeout which is 30 seconds. When we stop replication throughout the RollbackTest, this can cause delays when we wait for the stopReplProducer failpoint to be hit, since a getMore doesn't time out and return to the syncing node for 30 seconds even if there is no data to fetch. We can reduce this timeout inside RollbackTest by using this existing failpoint.
- is caused by
-
SERVER-37390 RollbackTestFixture doesn't need to wait for a new primary if it didn't shut down the current primary
- Closed
- related to
-
SERVER-41780 prepareTransaction doesn't always wait for write concern on retries
- Closed