[SERVER-84094] Implement initial drain policy for unsharded collections when the user specifies a destination shard Created: 12/Dec/23 Updated: 05/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | David Dominguez Sal |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||||||
| Sprint: | CAR Team 2024-01-22 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
When `draining` and `userSpecifiedDestination` are true, the unsharded balancer policy should generate migrations to move collections off of the draining shard and to `destinationShard`. This will require adding `userSpecifiedDestination` and `destinationShard` to the cluster statistics. The collections currently located on the draining shard can be fetched from config.collections/config.chunks in this initial implementation. This information can be fetched from the unsharded policy's cache later on, but this initial implementation will allow testing to start for removeShard. |