Config fuzzer suites barely test initial sync

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      These are all the config fuzzer suites we run as of Aug 2024:

      • antithesis_config_fuzzer_stress_concurrency_sharded_replication
      • config_fuzzer_concurrency_replication
      • config_fuzzer_concurrency_sharded_replication
      • config_fuzzer_concurrency_simultaneous_replication
      • config_fuzzer_jsCore
      • config_fuzzer_jstestfuzz_concurrent_replication
      • config_fuzzer_jstestfuzz_concurrent_sharded_continuous_stepdown
      • config_fuzzer_replica_sets_jscore_passthrough
      • config_fuzzer_sharding_jscore_passthrough
      • config_fuzzer_simulate_crash_concurrency_replication
      • config_fuzzer_stress_concurrency_replication
      • config_fuzzer_stress_concurrency_sharded_replication

      Although we added the initial sync method (logical / FCBIS) to the list of config fuzzer params, we don't actually run initial sync other than at the very beginning when we set up the cluster. It's not clear whether this very limited coverage was known / intentional.

              Assignee:
              Unassigned
              Reporter:
              Vishnu Kaushik
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: