[SERVER-24995] Mixed version shard JS testing of MigrationManager Created: 11/Jul/16 Updated: 20/Jul/16 Resolved: 20/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Kaloian Manassiev |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Sharding 17 (07/15/16), Sharding 18 (08/05/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Kaloian Manassiev [ 20/Jul/16 ] |
|
This task is better achieved through unit-tests instead of adding failpoints and will be done as part of |