[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:
Gantt Dependency
has to be done after SERVER-22659 Implement commitChunkMigration comman... Closed
has to be done after SERVER-24412 Create a CollectionMetadata::getChunk... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 16 (06/24/16)
Participants:

 Description   

Use the CollectionMetadata::getChunk method (SERVER-24412) to obtain the migrating chunk's version, and send it with the CommitChunkMigration command.

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 SERVER-24412 is not going to be done (because it won't work), this no longer needs to be done separately from SERVER-22659.

The CommitChunkMigration command specified in SERVER-22659 will assert that at least the chunk ranges are on the source shard – that the chunks are valid – before executing the migration commit. The command will not check the chunks' versions, which apparently are not stored anywhere except on the config server.

Generated at Thu Feb 08 04:06:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.