Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-76879

Config Fuzzer Enhancements

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Storage Execution

    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.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            matt.kneiser@mongodb.com Matt Kneiser
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated: