-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
With a couple of duplicate key error issues, it is observed that the oldest timestamp is moved ahead of the checkpoint timestamp in the last checkpoint and using that checkpoint while recovering lead to a miss a record.
Write a test to demonstrate that the oldest timestamp is moved ahead by delaying the checkpoint operation with timing stress functionality and observe the data consistency after restart. The timestamp_abort test can also be used/modified to develop the above test.
- is duplicated by
-
WT-7958 Include recovery in test/checkpoint
- Closed