[SERVER-28122] Persist config.collections entries on shards for the collections that shards possess Created: 27/Feb/17 Updated: 08/Mar/17 Resolved: 28/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
Shards need the collection shard key for filtering, eventually the collection UUID (will temporarily be the namespace until that project is complete), and a chunk version for secondary refresh (
It should be persisted in MetadataLoader::_initCollection, where we query the config server for the necessary config.collection entry. |