-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Reconciliation
-
None
-
Storage Engines, Storage Engines - Transactions
-
SE Transactions - 2025-11-21
-
3
Currently, when reconciliation fails, we do not release the page ID of the affected page, even if its contents have been written to disk. This results in an orphaned entry in the PALI, leading to complications during validation.
To address this issue, we can terminate the existing page ID and assign a new page ID for future use. While this solution resolves the problem, it breaks the delta chain since the next write will have to be a full page instead of a delta. However, I believe this approach is worthwhile as it simplifies the verification logic and streamlines data cleanup.
- is duplicated by
-
WT-15988 test/format (disagg.mode=leader) Delta chain validation failed
-
- Closed
-
- related to
-
WT-16027 Don't reset the page id if we failed reconciliation because of building an empty delta
-
- Closed
-
-
WT-16183 Add a counter for when we intentionally cut the delta chain
-
- Open
-
-
WT-15456 test/format (disagg.mode=leader) Transaction rollback assertion fires !WT_IS_METADATA(op->btree->dhandle)
-
- Closed
-
-
WT-15890 test/format (disagg.mode=leader) Assertion fires during rollback !WT_IS_METADATA
-
- Closed
-
-
WT-15988 test/format (disagg.mode=leader) Delta chain validation failed
-
- Closed
-
-
WT-15990 test/format (disagg.mode=leader, PALite) failed with Device or resource busy
-
- Closed
-