[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:
Gantt Dependency
has to be done after SERVER-24853 Refactor Balancer code to use Migrati... Closed
Related
is related to SERVER-22670 Unit-tests for the CSRS balancer Closed
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 SERVER-22670.

Generated at Thu Feb 08 04:07:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.