[SERVER-28265] drop collection on a shard must clear the shard's persisted chunk metadata in addition to the in-memory state Created: 09/Mar/17 Updated: 27/Oct/23 Resolved: 18/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-05-08, Sharding 2017-05-29 |
| Participants: |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 18/May/17 ] |
|
Chunk metadata is actually already handled here as part of the sharded ShardingCatalogClientImpl::dropCollection. setShardVersion is forcing a metadata refresh on all the shards. This happens after the collection data and config metadata have been cleared, so shard chunk metadata refresh gets NamespaceNotFound from the config server and the persisted metadata gets dropped by the shard chunk loader. |