-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding 17 (07/15/16), Sharding 18 (08/05/16)
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When the Balancer starts using the MigrationManager, we can add a failpoint at the end of _executeMigration and test that the expected migrations run each migration round. For example, if the several source shards are v3.2, then migrations for the same collection must run sequentially because each shard will take the distlock rather than the balancer.
- has to be done after
-
-
- Closed
-
- is related to
-
-
- Closed
-