[SERVER-32716] Dropping sharded database or collection leaves orphaned zone documents Created: 16/Jan/18 Updated: 06/Dec/22 Resolved: 09/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.18, 3.4.10, 3.6.2, 3.7.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 3 |
| Labels: | ShardingAutomationSupport | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When a database or collection is dropped in a sharded cluster, the drop code leaves around any zones which might have been defined. This is not only problematic because it leaves orphaned data around, but also because if the same collection is later recreated, the old zones will take effect possibly unknown to the user. |