-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
v4.4
-
Repl 2020-04-06
The unit test db_repl_test, more specifically: CheckUpdateSequencesAreIdempotent writes timestamps on modifies that are out of order. Could the test call rollback to stable between iterations? Or does it have to be this way?
For more detail see WT-5799.
- related to
-
SERVER-29944 Implement a basic idempotency checker for testing oplog idempotency
- Closed