-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Persistence
-
SE Persistence - 2025-11-21, SE Persistence - 2025-12-05
-
2
Following from 84189 and SERVER-113261, it has been identified that the current interval of creating a progress log during verify is too frequent. From the code:
typedef struct { uint64_t records_so_far; /* Records seen so far */ WT_ITEM *max_key; /* Largest key */ WT_ITEM *max_addr; /* Largest key page */ #define WT_VERIFY_PROGRESS_INTERVAL 100 uint64_t fcnt; /* Progress counter */ /* Configuration options passed in. */ wt_timestamp_t stable_timestamp; /* Stable timestamp to verify against if desired */ #define WT_VRFY_DUMP(vs) \ ((vs)->dump_address || (vs)->dump_blocks || (vs)->dump_layout || (vs)->dump_pages) bool dump_address; /* Configure: dump special */ bool dump_all_data; bool dump_key_data; bool dump_blocks; bool dump_layout, dump_tree_shape; bool dump_pages; bool read_corrupt;
We log every 100 keys. Realistically customer has order of magnitude more key than 100 keys in their database. This ticket aims to investigate ways to reduce the number of progress logs. There are few ways we can fix this:
- Increase progress interval to log more than X keys
- Change progress interval to timer (e.g. 5 seconds)
- Allow users to configure the interval
- Remove the message
- is depended on by
-
SERVER-113261 Check WT-15969 is limiting the log spam during validate()
-
- Blocked
-