Confirm that if and only if an FSM transaction successfully commits, that all of its writes appear in the database

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding 2018-09-24, Sharding 2018-10-08
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This was a missing piece of the concurrency testing in 4.0. We ensured that there were no transaction cycles, but not that all transactions that should have committed successfully committed.

      We should do this in as many workloads as makes sense.

      This will be especially useful in the sharding extension with KillSessions being called concurrently.

            Assignee:
            Janna Golden (Inactive)
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: