-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Checkpoints
-
None
-
Storage Engines
-
3
-
2024-08-06 - Withholding Tax
-
v8.0, v7.0
In WT-10979, new configuration items have been introduced for checkpoint cleanup:
- none (default behaviour)
- reclaim_space (new behaviour, sets the flag WT_CONN_CKPT_CLEANUP_SKIP_INT)
The intent is to force checkpoint cleanup not to skip pages when the reclaim_space mode is enabled.
However, in the current code, we do proceed with skipping the page if WT_CONN_CKPT_CLEANUP_SKIP_INT is set:
if (addr.type == WT_ADDR_LEAF_NO || (addr.ta.newest_stop_durable_ts == WT_TS_NONE && (F_ISSET(S2C(session), WT_CONN_CKPT_CLEANUP_SKIP_INT) || !F_ISSET(S2BT(session), WT_BTREE_LOGGED)))) { __wt_verbose_debug2( session, WT_VERB_CHECKPOINT_CLEANUP, "%p: page walk skipped", (void *)ref); WT_STAT_CONN_DSRC_INCR(session, checkpoint_cleanup_pages_walk_skipped); *skipp = true; }
- is caused by
-
WT-10979 Introduce configuration option to control checkpoint cleanup
- Closed