The check on the shard that the chunk's version sent by the config is the same as what the shard sees is a little counter productive: we bump the version of a random chunk on the donor with every migration, so a chunk that hasn't even moved away and back might get rejected for a moveChunk or splitChunk.
Instead, we should just compare the chunk's epochs to protect against moving a chunk on a collection that was dropped and recreated.
- is depended on by
-
SERVER-25673 Remove ChunkManager use in the MigrationManager
-
- Closed
-
- related to
-
-
- Closed
-
-
SERVER-27613 Remove unused 'chunkVersion' field sent in splitChunk command
-
- Closed
-