[SERVER-24996] 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: | Dianna Hohensee (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| 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, non-conflicting migrations should all run in parallel in a single round of migrations. |
| 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 |