-
Type:
Task
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: Checkpoints
-
Storage Engines
-
StorEng - 2025-01-21, StorEng - 2025-02-28
-
3
-
v8.0
We currently allow applications to configure obsolete cleanup to run between 60s and 100000s while the default value is 300s. This was done as part of WT-12657.
We should look into at least updating the lower bound. Lots of our tests don't run for more than 60s so setting to the current lowest bound still does not let us test the functionality.
Note: The component is checkpoint but that's misleading from 8.0 since checkpoint cleanup is no longer part of checkpoint.
- causes
-
WT-14261 checkpoint_cleanup.wait values from develop is not compatible with 8.0
-
- Closed
-
- is depended on by
-
SERVER-98384 Lower minimum checkpoint_cleanup time to match wiredtiger minimum
-
- Closed
-
- is related to
-
WT-12643 Fix Eviction Server walk logic so that it's able to evict all pages
-
- Closed
-
-
WT-14230 Add configuration option to dynamically disable WT-12643
-
- Closed
-
-
WT-12657 Add checkpoint cleanup utility thread
-
- Closed
-
-
SERVER-98384 Lower minimum checkpoint_cleanup time to match wiredtiger minimum
-
- Closed
-
- related to
-
WT-13216 Assess the use of cache eviction check in compact
-
- Closed
-
-
WT-13283 Fix the cache aggressive mode not to show the garbage value
-
- Closed
-
-
WT-13291 Incorrect timestamps printed in RTS logs and contradictory ones
-
- Closed
-
-
WT-13716 Fast truncated pages on HS during selective backup not removed
-
- Closed
-
-
WT-13244 Lock the ref after we have acquired the prefetch lock
-
- Closed
-
-
SERVER-98384 Lower minimum checkpoint_cleanup time to match wiredtiger minimum
-
- Closed
-
-
WT-12096 __rec_validate_upd_chain(): Do not return EBUSY if globally visible.
-
- Closed
-