-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Testing Infrastructure
-
None
-
Fully Compatible
-
TIG 2018-04-23
It should do updates of the form
{$push: {order: {tid: tid, txnNumber: txnNumber, nDocs: nDocs}}
to establish the relative commit order of transactions executed by the different worker threads. Including the number of documents to be updated as part of the transaction makes it possible that at any point in time, a consistent snapshot of the database should see both (1) a consistent order of elements in the "order" array and (2) exactly nDocs containing that element. These properties should be checked as part of the $config.teardown() function after all of the transactions have completed. SERVER-34294 will be follow-up work to have these properties checked periodically while varying the read concern level via another state function.
- depends on
-
SERVER-34292 Add JavaScript class for representing graph and doing cycle detection
- Closed
- is depended on by
-
SERVER-35263 Add FSM workloads for testing atomicity and isolation of updates inside a transaction across multiple collections and databases
- Closed
- is duplicated by
-
SERVER-34294 Extend multi_statement_transaction_commit_order.js FSM workload to check consistency periodically
- Closed