Create integration tests that do rollbacks with potentially problematic sequences of operations

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2017-10-02, Repl 2017-10-23
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      (updated description)
      This will be implemented in C++ as an end-to-end unit test for the new rollback algorithm.

      ------

      Various commands, especially collection metadata commands, can cause rollback failures if they occur in the right order on the rolling-back node or the node's sync source. We should create a suite of tests for the known problematic operation sequences and another suite that runs random operations on both the rollback node and its sync source to catch unknown problematic scenarios.

      The random test should log all operations it runs for maximum debuggability. Both should include a consistency check at the end.

              Assignee:
              Will Schultz
              Reporter:
              Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: