[SERVER-74982] Automatically Migrate Jumbo Chunks From a Draining Shard Created: 17/Mar/23 Updated: 12/Dec/23 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Panton | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, sharding-emea-pm-review, shardingemea-qw, ts-product-report-sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Participants: | |
| Story Points: | 3 |
| Description |
|
Today Currently the balancer does not migrate jumbo chunks from a draining shard. This can cause Atlas configuration changes to become stuck and leave customers confused as they've forgotten or don't know that they have jumbo chunks on the draining shard. Story As a MongoDB sharding customer I would like the balancer to automatically migrate jumbo chunks from a draining shard so that I do not have connect to the cluster and run manual commands via mongosh. Future When a customer requests a shard to be removed from a cluster the balancer will automatically migrate jumbo chunks from the draining shard. |