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

Create multi-client fuzzer

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution

      Currently we don't have a multi-client (concurrent) fuzzer that can issue multiple commands against the server in parallel. As a result the fuzzer isn't as good at producing deadlocks as it could be.

      For example, in SERVER-89730 we see that two concurrent cloneCollectionAsCapped can deadlock (and can potentially deadlock with renameCollection and some other sharded DDL operations) if the arguments are provided in reverse order. This seems like something the fuzzer would be good at catching.

            Assignee:
            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            Reporter:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: