Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
4.5.1
-
Fully Compatible
-
ALL
-
Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-10
-
40
Description
Right now, if _configsvrCommitChunkMigration is run twice upon the config server, the second call results in an error even if the migration actually succeeded.
Possible fixes:
- On the config server, checking both donor and recipient in checkChunkMatchesRequest
- On the shard, double check that the chunk is still owned before a call to _configsvrCommitChunkMigration (it doesn't make the command idempotent, but it guarantees that it doesn't get called more than once)
Attachments
Issue Links
- causes
-
SERVER-50215 _configsvrCommitChunkMigration might return before changes are majority committed
-
- Closed
-
-
SERVER-50458 Re-enable retryability of commitChunkMigration on the config server
-
- Closed
-
-
SERVER-50577 Return actual donor shard version in getShardAndCollectionVersion
-
- Closed
-