[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:
Duplicate
duplicates SERVER-35441 drop/dropDatabase does not cleanup co... Closed
Related
related to SERVER-8619 Drop of collection or database should... Closed
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 SERVER-35441 into fast cluster resize.

Comment by Randolph Tan [ 26/Jun/18 ]

dup of SERVER-35441?

Generated at Thu Feb 08 04:41:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.