[SERVER-6350] Do not allow completely removing tag from all shards if currently in use (in config.tags collection) Created: 08/Jul/12 Updated: 06/Dec/22 Resolved: 31/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Sharding |
| Affects Version/s: | 2.1.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | balancer, sharding, tags | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
If you remove a tag from all shards, but it still exists for a chunk (config.tags collection) then the chunk can not be migrated and causes errors during balancing, until the tag is added to a shard. When removing a tag from a shard we should validate that it is not used by any chunks (config.tags collection) and if it is then it must not be the last shard with that tag. |