[SERVER-34826] Write targeted FSM workload for read repeatability in transactions Created: 03/May/18 Updated: 29/Oct/23 Resolved: 06/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc5, 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Jonathan Abrahams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||
| Sprint: | TIG 2018-06-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||
| Description |
|
We should write an FSM workload that verifies read repeatability of transactions. This workload can presumably have each thread be in either a Read or Update state, where the Read state executes multiples reads sequentially, expecting to see the same result set for each read. The Update state could update some random subset of documents in a collection. This test would be good at verifying repeatability under higher concurrency and load than our targeted tests. Eventually we may also add a repeatability test that runs against all our existing FSM workloads, but in lieu of that, this could be a valuable targeted workload to exercise a key property of transactions under snapshot isolation. |
| Comments |
| Comment by Githook User [ 07/Jun/18 ] |
|
Author: {'username': 'hptabster', 'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com'}Message: (cherry picked from commit 16b09c6fa4ff74af2310ed73f0187fcd95fd3e89) |
| Comment by Githook User [ 06/Jun/18 ] |
|
Author: {'username': 'hptabster', 'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com'}Message: |