[SERVER-33324] Add support to benchRun for including txnNumber on read commands Created: 12/Feb/18 Updated: 29/Oct/23 Resolved: 14/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Storage 2018-02-12, Storage 2018-02-26 | ||||
| Participants: | |||||
| Description |
|
Add a new option to benchRun that will cause it to keep an always-incrementing transaction number for each workload thread and send that as a txnNumber for all finds. The same transaction number must be used for subsequent getMores. This is similar to the useIdempotentWrites option used for write commands. This is needed for testing snapshot reads because they must be run in transactions. |
| Comments |
| Comment by Githook User [ 14/Feb/18 ] |
|
Author: {'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}Message: |
| Comment by David Daly [ 12/Feb/18 ] |
|
If you could do it, that would be great. |
| Comment by Tess Avitabile (Inactive) [ 12/Feb/18 ] |
|
david.daly, should I do this work to support PERF-1331, or should it be done by the perf team? |