-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Metadata
-
Security Level: Public (Available to anyone on the web)
-
Storage Engines - Transactions
-
162.444
-
SE Transactions - 2026-08-28
-
3
In a lot of places, we check if the btree is the metadata or not using WT_IS_METADATA macro. However, with the new disagg metadata, we should check that as well. Review the code base to ensure to also check the disagg metadata when where it is needed.
To ensure we don't forget about that in the future, we should create a new macro that checks both the metadata and the disagg metadata.
- is duplicated by
-
WT-18379 Places that check the metadata file but miss the disaggregated shared metadata
-
- Closed
-
- is related to
-
WT-15292 disagg: test_bug033.py, test_prepare{22,23,27}.py crash in __wt_tree_modify_set called by rollback_to_stable
-
- Closed
-
-
WT-18379 Places that check the metadata file but miss the disaggregated shared metadata
-
- Closed
-
-
WT-15117 test_hs08 failed as more than expected writes were squashed
-
- Closed
-
-
WT-18049 test_bug010.test_checkpoint_dirty: timestamp usage check aborts during checkpoint on WiredTigerShared.wt_stable
-
- Closed
-
-
WT-18364
Add a combined WT_IS_ANY_METADATA() macro for handles that are either metadata tree
-
- Closed
-