-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Checkpoints
-
Security Level: Public (Available to anyone on the web)
-
Storage Engines - Persistence
-
3,288.364
-
SE Persistence backlog, SE Persistence - 2026-04-24
-
None
The checkpoint order variable is guaranteed to be strictly increasing if all the checkpoints are written by the same node. However, in the case of disagg, nodes can step-up and step-down and writing to the same shared storage (SLS). We need to ensure the checkpoint orders are also strictly increasing if the checkpoints are written by different nodes.
- depends on
-
WT-17143 Explicitly disable read-only connections with disagg and track support as a feature request
-
- Closed
-
- is related to
-
WT-17093 Redefine the rules of checkpoint order for fake checkpoint
-
- Open
-
-
WT-17232 test_prepare33 checkpoint_and_verify_stats assertion error
-
- Blocked
-
- related to
-
WT-17599 Strict file checkpoint order check without timestamp
-
- Blocked
-