[SERVER-82153] Add reshardingCount to the data object in the resharding FSM workload Created: 12/Oct/23 Updated: 28/Nov/23 Resolved: 28/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kruti Shah | Assignee: | Kruti Shah |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
The resharding workload limits the number of operations that can occur and to track the number of executions, there is a variable called reshardingCount. The reshardCollection command is condition to run when the reshardingCount is less than the max number of executions. Currently the reshardingCount is not initialized and it returns as "undefined" causing the reshard operation to never run in the fsm workload. Add reshardingCount to the data object here. |
| Comments |
| Comment by Githook User [ 21/Nov/23 ] |
|
Author: {'name': 'Kruti Shah', 'email': 'kruti.shah@mongodb.com', 'username': 'krutishah139'}Message: |