Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
None
-
ALL
-
Repl 2019-12-16, Repl 2019-12-30, Repl 2020-01-13
-
6
Description
We already take into account that some rollbacks may not occur during rollback shutdown tests
However, we don't take into account that these rollbacks that don't happen may include prepared transactions, which prevent us from doing data consistency checks. In rollback tests with shutdowns we must account for rolled-back prepared transactions possibly still being around, and abort them explicitly or skip consistency checks.
Attachments
Issue Links
- duplicates
-
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-37390 RollbackTestFixture doesn't need to wait for a new primary if it didn't shut down the current primary
-
- Closed
-
-
SERVER-42650 Remove stale comments mentioned in the RollbackTest for "transitionToSteadyStateOperations" state.
-
- Closed
-