[SERVER-76343] modify stopBalancer to explicitly wait for the completion of outstanding migrations Created: 20/Apr/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Sprint: | Sharding EMEA 2023-05-15 | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
The stopBalancer is a synchronous command which returns the control to the user once the Balancer thread has ended or interrupted its most recent round of chunk migrations. This behaviour does not always guarantee that once the control is returned, there won't be any shard that is still serving a chunk migration issued by the balancer. The implementation of stopBalancer may be modified to add such guarantee. |