Move the cache of block handles out of the WT_BLOCK and into the block manager (i.e., into WT_BM). This will provide an initial implementation of the block handle table described in the Technical Design for PM-2956.
This means that the block manager layer will now crack and interpret address cookies.
On write, the block handle (WT_BLOCK) will still generate the cookie. It is reasonable for a WT_BLOCK to know its own ObjectID.
- duplicates
-
WT-10462 Change block manager to track all of the WT_BLOCKs for a tree
- Closed
- is depended on by
-
WT-9823 Fix race between read and delete of WT_BLOCK in tiered storage
- Closed
-
WT-10838 Track active read count for tiered storage block handles
- Closed
- related to
-
WT-10763 Don't load the wrong extent lists in __wt_block_checkpoint_load
- Closed
-
WT-10823 Fix btree_stat_init failure for tiered storage in test/format.
- Closed
-
WT-11181 heap-use-after-free during dhandle open
- Closed