Files
mongo/buildscripts/resmokelib/config_fuzzer_wt_limits.py
Louis Williams 399edb27b1 SERVER-100869 Remove config fuzzer stress (#32450)
GitOrigin-RevId: 74309e403e8f2a0e8836484bd662645d3ed4b6ed
2025-04-09 21:14:00 +00:00

131 lines
6.3 KiB
Python

"""Minimum and maximum declarations for all WiredTiger parameters that are supported by the config fuzzer."""
"""
How to add a fuzzed WiredTiger parameters:
Below is a list of ways to fuzz configs which are supported without having to also change buildscripts/resmokelib/mongo_fuzzer_configs.py.
Please ensure that you add it correctly to the "wt" (eviction parameters) or "wt_table" subdictionary.
Let choices = [choice1, choice2, ..., choiceN] (an array of choices that the parameter can have as a value).
The parameters are added in order of priority chosen in the if-elif-else statement in generate_normal_wt_parameters() in
buildscripts/resmokelib/mongo_fuzzer_configs.py.
1. param = rng.choices(choices), where choices is an array
Add:
"param": {"choices": [choice1, choice2, ..., choiceN]}
You can also add a "multiplier" key which multiplies the key by the multiplier value.
param = rng.choice(choices) * multiplier
Add:
"param": {"choices": [choice1, choice2, ..., choiceN], "multiplier": multiplier}
2. param = rng.randint(min, max)
Add:
“param”: {“min”: min, “max”: max}
If you have a parameter that depends on another parameter being generated (see eviction_target needing to be initialized before
eviction_trigger as an example in buildscripts/resmokelib/mongo_fuzzer_configs.py) or behavior that differs from the above cases,
please do the following step:
1. Add the parameter and the needed information about the parameters here (ensure to correctly add to the wt or wt_table sub-dictionary)
In buildscripts/resmokelib/mongo_fuzzer_configs.py:
2. Add the parameter to excluded_normal_parameters in the generate_eviction_configs() or generate_table_configs()
3. Add the parameter's special handling in generate_special_eviction_configs() or generate_special_table_configs()
Note: The main distinction between min/max vs. lower-bound/upper_bound is there is some transformation involving the lower and upper bounds,
while the min/max should be the true min/max of the parameters. You should also include the true min/max of the parameter so this can be logged.
If the min/max is not inclusive, this is added as a note above the parameter.
"""
target_bytes_min = 50 * 1024 * 1024 # 50MB # 5% of 1GB default cache size on Evergreen
target_bytes_max = 256 * 1024 * 1024 # 256MB # 25.6% of 1GB default cache size on Evergreen
# We want eviction_dirty_trigger and eviction_updates_trigger >= 64MB. See SERVER-96683.
min_trigger_bytes = 64 * 1024 * 1024 # 64MB # 6.4% of 1GB default cache size on Evergreen
config_fuzzer_params = {
# WiredTiger's debug_mode offers some settings to change internal behavior that could help
# find bugs. Settings to fuzz:
# eviction - Turns aggressive eviction on/off
# realloc_exact - Finds more memory bugs by allocating the memory for the exact size asked
# rollback_error - Forces WiredTiger to return a rollback error every Nth call
"wt": {
# The following three parameters are for fuzzing file manager settings.
"close_idle_time_secs": {"min": 1, "max": 100},
"close_handle_minimum": {"min": 0, "max": 1000},
"close_scan_interval": {"min": 1, "max": 100},
"dbg_eviction": {"choices": ["true", "false"]},
"dbg_realloc_exact": {"choices": ["true", "false"]},
"dbg_rollback_error": {
"min": 0,
"max": 1500,
"lower_bound": 250,
"upper_bound": 1500,
"choices": [0],
},
# 1% of 1GB default cache size on Evergreen, 99% of 1GB default cache size on Evergreen
"eviction_checkpoint_target": {"min": 10 * 1024 * 1024, "max": 990 * 1024 * 1024},
# 50% of 1GB default cache size on Evergreen, 95% of 1GB default cache size on Evergreen
"eviction_target": {"min": 500 * 1024 * 1024, "max": 950 * 1024 * 1024},
"eviction_trigger": {
"lower_bound": 1,
# 99% of 1GB default cache size on Evergreen
"upper_bound": 990 * 1024 * 1024,
"min": "(eviction_target + 1)",
"max": 990 * 1024 * 1024,
},
"eviction_dirty_target": {
"min": target_bytes_min,
"max": target_bytes_max,
},
"eviction_dirty_trigger": {
"min": "max(eviction_dirty_target + 1, min_trigger_bytes)",
"max": "trigger_max",
},
# eviction_updates_target/trigger are relative to previously fuzzed values.
"eviction_updates_target": {
"min": "updates_target_min",
"max": "eviction_dirty_target - 1",
},
"eviction_updates_trigger": {
"min": "max(eviction_updates_target + 1, min_trigger_bytes)",
"max": "eviction_dirty_trigger - 1",
},
"trigger_max": {"default": target_bytes_max},
# We fuzz eviction_updates_target and eviction_updates_trigger using updates_target_min. These are
# by default half the values of the corresponding eviction dirty target and trigger. They need to stay
# less than the dirty equivalents. The default updates target is 2.5% of the cache, so let's start fuzzing
# from 2%.
"updates_target_min": {"default": 20 * 1024 * 1024},
},
"wt_table": {
"block_compressor": {"choices": ["none", "snappy", "zlib", "zstd"]},
# The following three parameters get multipled by their multiplier after the choice in choices is made.
"internal_page_max": {
"choices": [4, 8, 12, 1024, 10 * 1024],
"min": 4 * 1024,
"max": 10 * 1024 * 1024,
"multiplier": 1024,
},
"leaf_page_max": {
"choices": [4, 8, 12, 1024, 10 * 1024],
"min": 4 * 1024,
"max": 10 * 1024 * 1024,
"multiplier": 1024,
},
"leaf_value_max": {
"choices": [1, 32, 128, 256],
"min": 1 * 1024 * 1024,
"max": 256 * 1024 * 1024,
"multiplier": 1024 * 1024,
},
"memory_page_max_upper_bound": {
"min": (256 * 1024 * 1024) / 10,
"max": (1024 * 1024 * 1024) / 10,
"multiplier": 1024 * 1024,
"lower_bound": 256,
"upper_bound": 1024,
},
"prefix_compression": {"choices": ["true", "false"]},
"split_pct": {"choices": [50, 60, 75, 100], "min": 50, "max": 100},
},
}