The logic in the MigrationSourceManager here should be fixed. CollectionMetadata::getNextChunk won't necessarily return a chunk with the minKey given, but can also return the next chunk with a minKey higher than the given one. The use in MigrationSourceManager does not seem to account for this.
- related to
-
SERVER-26372 If a chunk has been split since a moveChunk was sent to a shard, you can get an error message with "This indicates corrupted metadata"
-
- Closed
-