[SERVER-64288] read write workload to run concurrent with cluster balancing Created: 07/Mar/22 Updated: 29/Oct/23 Resolved: 19/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lamont Nelson | Assignee: | Lamont Nelson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding NYC 2022-04-04, Sharding NYC 2022-04-18, Sharding 2022-05-02 | ||||||||
| Participants: | |||||||||
| Story Points: | 4 | ||||||||
| Description |
|
We want to have the ability to run concurrent r/w workload while the cluster is balancing. We should be able to coordinate the start/end of the clients applying their workload and collect the operation metrics afterwards. Parameters: |
| Comments |
| Comment by Lamont Nelson [ 14/Mar/22 ] |
|
I copied this over from the duplicate ticket. |
| Comment by Lamont Nelson [ 14/Mar/22 ] |
|
Rachita Dhawan We'll want the clients to perform our various types of data modification operations with parameterized percentages of each operation type. We'll want to be able to specify: For transactions, it probably makes sense to have a parameter for # documents updated per transaction, and we can set this to 1 if we need to have an apples to apples comparison to regular write operations. |