-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Block Cache, Statistics
-
None
-
Storage Engines - Persistence
-
87.51
-
StorEng - Defined Pipeline
-
None
Seven stats describe the disaggregated victim cache but live under BlockCacheStat with a block_cache_ prefix: block_cache_puts, _app_thread_puts, _put_time, _app_thread_put_time, _put_time_max, _cold_not_cached, _put_failures. They were never block cache stats, all seven were added as victim cache stats (WT-17850, WT-17854, WT-17815, WT-18696) and their descriptions already say "disaggregated victim cache".
Move them to DisaggStat as disagg_victim_cache_* and drop the now-redundant "disaggregated" from the descriptions.
This moves them in serverStatus().wiredTiger from block-cache to disagg, since MongoDB keys that output by the stat description. Nothing consumes them today, checked mongo outside third_party (including the curated allowlist in WiredTigerKVEngine::collectStorageStats) and t2, whose 22 block-cache descriptors are all genuine block cache stats.
- is related to
-
WT-17815 Ensure pages from cold collections never enter the block cache
-
- Closed
-
-
WT-17850 Investigate whether application threads should contribute to the disaggregated victim cache during eviction
-
- Closed
-
-
WT-17854 Add block_cache_put_time_max statistic for worst-case victim cache put latency
-
- Closed
-
-
WT-18696 Add stat to track block cache put failures
-
- Closed
-