-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
v4.0
-
Sharding 2018-06-04, Sharding 2018-06-18, Sharding 2018-07-16, Sharding 2018-07-30
-
0
Three things:
fromShard is a connection string – misleading. _recvStartChunk should get a ShardId rather than a connection string, then the MigrationDestinationManager can get connection strings from the ShardRegistry. There's a ScopedDbConnection conn object that shouldn't be used anymore: use the ShardRegistry and Shard.
Start actually using StartChunkCloneRequest::createFromCommand, which is currently used no where.
Generally clean up the MigrationDestinationManager – e.g., we have "_from = fromShard" local variable, but pass fromShard through functions anyway.
- causes
-
SERVER-38751 _migrateClone and _transferMods incorrectly labeled as idempotent in MigrationDestinationManager
- Closed
- is depended on by
-
SERVER-22674 Support multiple incoming migrations on the same shard
- Closed
-
SERVER-35074 Write unit-tests which exercise the chunk migration protocol between two shards end-to-end
- Closed
- related to
-
SERVER-43443 Remove outdated TODO reference in the MigrationDestinationManager
- Closed