[SERVER-43179] Balancer should not try to clone data if a shard is in forced draining mode Created: 05/Sep/19 Updated: 06/Dec/22 Resolved: 03/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
When a shard is put into forced draining mode, the balancer should schedule any chunks on this shard to be moved off of it. Since the shard is completely down, we cannot actually move any data over so we should skip the clone phase of the migration and just execute the metadata update on the config server. |
| Comments |
| Comment by Sheeri Cabral (Inactive) [ 03/Jan/20 ] |
|
We have abandoned the project associated with this work - PM-1477. |