Loading...

XML

Word

Printable

JSON

Summary: For this ticket SERVER-89046: Consider fuzzing WT stress parameters, we were looking to fuzz some WiredTiger stress parameters (specifically, all the parameters labeled __checkpoint_timing_stress in this file) to take on values {0, … , K} instead of just having the values be set {0, K} (where K is the value that is set for the parameter when the stress is turned on).
We want to try driving fuzzing from outside the server. We would like the server to pass the configs down to WT in its config string to wiredtiger_open().
Some reasons why we want to approach this ticket through this method is so that resmoke can log the chosen parameters, which would be helpful for people using the config fuzzer tool.
We want to check-in if the WT team is open to configuring these params externally.
Furthermore, there is a lack of documentation about the different stress parameters and their purpose; we would like to further discuss what stress parameters specifically would be helpful to toggle for config fuzzer testing.

A definition of done: A list of the different stress parameters that would make the most sense to change and fuzz out of the entire list of stress parameters and a discussion of whether it is possible to configure the WT parameters externally or if it would make more sense to directly change the WiredTiger repos to fuzz the parameters and to report these fuzzed parameters back to the server for logging purposes.

- In the case that we cannot pass in WT stress parameters externally, a definition of done would be implementing the fuzzing through WT and then being able to report the fuzzed parameters to the server for logging purposes.

is depended on by

SERVER-89046 Consider fuzzing WT stress parameters