FSM workloads with replication should be completed on secondary before next workload runs

XMLWordPrintableJSON

    • Fully Compatible
    • CAP - 3.1.5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      FSM workloads which run in replication, may still be running on a secondary after teardown has occurred on the primary. This means a subsequent workload may be impacted by a previous one. Additional protection during workload completion is required to ensure the workload has completed it's operations (insert document with write concern of all?).

            Assignee:
            Jonathan Abrahams (Inactive)
            Reporter:
            Ian Whalen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: