[SERVER-34294] Extend multi_statement_transaction_commit_order.js FSM workload to check consistency periodically Created: 04/Apr/18 Updated: 18/Apr/18 Resolved: 18/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | TIG 2018-04-23 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
A new state function should be added to the multi_statement_transaction_commit_order.js FSM workload that checks there is both (1) a consistent order of elements in the "order" array and (2) exactly nDocs containing that element. The read concern level to use when starting the transaction can be varied because the changes from |
| Comments |
| Comment by Spencer Brody (Inactive) [ 17/Apr/18 ] |
|
sgtm |
| Comment by Max Hirschhorn [ 17/Apr/18 ] |
|
We'll definitely do more testing work when we change the read concerns to have different meanings that I'm inclined to just revisit this work under a future SERVER ticket. |
| Comment by Judah Schvimer [ 17/Apr/18 ] |
|
Since all transaction read concerns up-convert to "snapshot", I don't think doing that would add any extra coverage currently, though as we change the semantics around those other read concerns, adding them to the workload would definitely be good. |
| Comment by Max Hirschhorn [ 16/Apr/18 ] |
|
spencer, judah.schvimer, the changes from 239f4fa as part of |