[SERVER-24413] Send ChunkVersions with the CommitChunkMigration command, which will then check them 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: | Duplicate | 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 |
|
Use the CollectionMetadata::getChunk method ( The CommitCHunkMigration command should parse the ChunkVersions from the command request, and execute queries to config.chunks to check that the chunks are valid, i.e. exist in the collection. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 07/Jun/16 ] |
|
Since The CommitChunkMigration command specified in |