Check previous config fuzzer assignments are consistent with current config fuzzer and add true min and maxes to each param

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2024-08-19
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      {{maxNumberOfTransactionOperationsInSingleOplogEntry }}in the config fuzzer increased by *10 when refactoring the config fuzzer in double-check that the config fuzzer parameters are consistent with previous assignments.

      Also, it would be nice to have the true min/maxes for each parameter to avoid this issue in the future and for logging purposes.

            Assignee:
            Stephanie Eristoff
            Reporter:
            Stephanie Eristoff
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: