-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines - Foundations
-
44.779
-
None
-
None
Characterize the checkpoint-to-checkpoint risk when tables awaiting publication cannot be evicted, and validate that bulk-load workloads do not create cache pressure.
A table created while a stable schema epoch is set carries WT_BTREE_AWAITS_PUBLISH, which disables eviction until a checkpoint (or, with WT-18092, the eviction server) observes that the stable schema epoch covers the table's published CREATE entry. Until then, all of the table's data is pinned in cache. This work should:
- Measure how much dirty data an unpublished table can pin between checkpoints under realistic checkpoint intervals.
- Validate that create-and-bulk-load workloads before the first covering checkpoint do not stall on cache pressure.
- Cover both the pre-publish window (eviction must stay disabled) and the post-publish window (eviction should proceed once the stable schema epoch covers the create).