[SERVER-24412] Create a CollectionMetadata::getChunk method. Created: 06/Jun/16 Updated: 05/Apr/17 Resolved: 07/Jun/16 |
|
| 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: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 16 (06/24/16) | ||||||||
| Participants: | |||||||||
| Description |
|
This is motivated by: The MigrationSourceManager needs to be able to access the chunk it is migrating's ChunkVersion. That version will then be sent with the CommitChunkMigration command. The CommitChunkMigration command will then do a query to check that the chunks it receives are valid, i.e. exist in the config.chunks collection. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 07/Jun/16 ] |
|
This won't actually work as intended because the CollectionMetadata only stores chunk ranges, not ChunkVersions. Closing. |