-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Test Checkpoint
-
None
-
Storage Engines, Storage Engines - Transactions
-
SE Transactions - 2025-09-26, SE Transactions - 2025-11-21
-
5
With precise checkpoint and preserve prepared on, we want to add to test/checkpoint the ability open the live database, claim the prepared update and then do the validation.
Some discussion points from a chat with Jie and Sid when going through the discussion about precise checkpoint to consider:
Checking if reconciled data before stable timestamp is done in test/format (how about prepare?) - Done through Mirrored table
- What if all mirrored tables are reconciled wrongly? (Testing gap (Infrastructure is not there))
Scenario: Recovery + Review all claimed prepared transactions (Randomly rollback/commit?) - Rule?: Open cursor and insert is this allowed -> check pls
- Testing coverage: All mirrored tables should have the exact same claim prepared data.
- What if all tables are wrong? (Testing gap) (Testing gap (Infrastructure is not there))
To cover testing gap use _abort csuite tests: - Making sure all data is reconciled properly? Add Prepare ID file, commit (Preserve prepare) * Record all data before stable timestamp -> crash -> make sure all correct data is there (Add support for precise checkpoint)
- Can we check if pending prepared before stable timestamp is checkpointed?
- causes
-
WT-16068 model-test-long-random-config passing invalid arguments to model test binary
-
- Closed
-