[SERVER-27703] Design schema for admin.chunks Created: 17/Jan/17 Updated: 18/Jan/17 Resolved: 18/Jan/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: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 2017-01-02 | ||||||||
| Participants: | |||||||||
| Description |
|
Figure out what chunk metadata information should be sent to secondaries. Consider refining the chunk metadata information that shards maintain. Notes: the admin.chunks collection has a dual purpose, to propagate information to secondaries and to be read from on startup/full reload. |