[SERVER-59967] Remove the guard against "multiple moveChunk commands executed by the same shard" from BalancerCommandsScheduler Created: 15/Sep/21 Updated: 29/Oct/23 Resolved: 20/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| 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: | Sharding EMEA 2021-09-20 | ||||
| Participants: | |||||
| Linked BF Score: | 150 | ||||
| Description |
|
The BalancerCommandsScheduler includes logic to ensure that there cannot be more than one moveChunk command involving a certain shard (either as a donor or recipient) under execution. Such check is useless (since it is already present in a higher level component , where the condition is guaranteed to be valid also for moveChunk commands issued by the MigrationManager) and it should be removed. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |