[SERVER-76879] Config Fuzzer Enhancements Created: 05/May/23  Updated: 06/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Matt Kneiser Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 1
Labels: storex-ranked, techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-70343 Make time series tests resilient to WCEs Open
Assigned Teams:
Storage Execution
Participants:

 Description   

After triaging, reviewing, debugging, and interacting with several config fuzzer Hot BFs this week, here is a list of proposals from a few members of StoreEx on how to improve the config fuzzer so that a server engineer can find root causes of test failures quicker:

  • WT string split to multiple lines
    • Currently the WT config string is on one line which make diffing error-prone and time-consuming
  • show defaults, min/max for each setting inline
    • Configs can be surprising on first glance (a negative number?? must be a problem!)
    • Showing some of this background can illuminate how extreme or unusual the fuzzed parameter is
  • have fuzz seed be consistent across branches
    • currently, a fuzz seed does not generate the same configs on all commits nor branches. This makes comparisons hard to carry out.


 Comments   
Comment by Matt Kneiser [ 05/May/23 ]

It would also be convenient (I would say necessary) to dump the config parameters in BFs, this is currently a manual process.

Generated at Thu Feb 08 06:33:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.