-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Cache and Eviction
-
None
-
Storage Engines - Transactions
-
138.858
-
SE Transactions - 2026-11-20
-
3
Problem
incremental_app_eviction, prefer_scrub_eviction and skip_update_obsolete_check under eviction=(...) are accepted by WT_CONNECTION.reconfigure, but the eviction config parse only sets their flag in cache->cache_eviction_controls when the value is true and does nothing when it is false. Once one of them is turned on, reconfiguring it to false leaves it on.
test_cache_evict_config01.py reconfigures these options both ways but only checks that the connection still works, so it does not catch this.
Proposed change
- Clear the flag when the value is false, as eviction.bounded_wake does (
WT-18961). - Extend test_cache_evict_config01.py to check that each flag is actually cleared after reconfiguring it off, for example through a debug-visible statistic or a behaviour the option controls.
Definition of done
Turning each option on and then off with reconfigure leaves it off, and a test fails if the clear is removed.
- related to
-
WT-18961 Wake a bounded number of eviction waiters instead of broadcasting on every queue push
-
- Closed
-