-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Test Format
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - 2025-08-01, SE Foundations - 2025-07-04, SE Foundations - 2025-07-18
-
8
Previous tickets added leader and follower mode to test/format. We need a way to test both, and transitions between them. When we are testing using "switch", we'll start in either leader or follower mode, and periodically switch between them. Leaders can do checkpoints, followers cannot.
When switching from leader to follower (step-down), any data modified since the last checkpoint is disregarded (i.e. gets lost). This is part of the WT contract behavior. For test/format, it means that at a step-down, we need to lost knowledge of recent changes that have been performed (they care kept in the "snap" data structure). Normally "snap" is used to re-read data that has been recently written to verify that it is still there. Since it won't be, the safest course of action (to get successful runs) is to zero out the snap at step-down. There may be some thread coordination to pull this off.
- is related to
-
WT-15088 Commit may be rolled back after we have logged the transaction
-
- Closed
-
-
WT-15094 Fix - Update the assert to check if the btree leaf is delta enabled.
-
- Closed
-
-
WT-15106 Make cache walk heuristic reset specific to disaggregated storage
-
- Closed
-
-
WT-15005 Revisit configuration options related to page deltas and make changes as necessary
-
- Closed
-
-
WT-15033 Optimize cursor->reset calls during search() and search_near() in DSC
-
- Closed
-
- related to
-
WT-15100 Make switch mode follower settings configurable in format
-
- Open
-