[SERVER-35806] Dropping a collection should remove the zones associated with the collection Created: 26/Jun/18 Updated: 06/Dec/22 Resolved: 26/Jun/18 |
|
| 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: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
After a sharded collection is dropped, we should then remove the zones associated with the collection. We should always attempt to drop the zones, regardless of whether the collection was found or not. |
| Comments |
| Comment by Janna Golden [ 26/Jun/18 ] |
|
Oh yeah I'll close this and move |
| Comment by Randolph Tan [ 26/Jun/18 ] |
|
dup of |