[SERVER-43181] Error if removeShard command run with forceRemoveByAbandoningData for a shard that is the only shard associated with a zone 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 |
|
Currently if a shard is in draining mode but is the only shard in a particular zone, the balancer will just skip this chunk and the command will never return "completed". If removeShard is run with the the forceRemoveByAbandoningData option, we should fail the command in this case and inform the user they must add a new shard to this zone. We cannot add a shard to this zone automatically due to various restrictions (i.e. GDPR), and it is unacceptable in this case for the shard to remain in forcedDraining mode. |
| Comments |
| Comment by Sheeri Cabral (Inactive) [ 03/Jan/20 ] |
|
We have abandoned the project associated with this work - PM-1477. |