[SERVER-25202] Make MigrationManager able to schedule new migrations while there are migrations outstanding Created: 21/Jul/16 Updated: 02/Sep/16 Resolved: 12/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 18 (08/05/16), Sharding 2016-08-29 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
In order to be able to support multiple manual moveChunk requests for the same collection (but different shards) we need to change the API of the MigrationManager so new migrations can be scheduled on it, while there are migrations outstanding. In order to do this, we will introduce a scheduleMigration(MigrationRequest) method, which will return a Notification object, which can be waited on for the purposes of obtaining the results of that migration request. |
| Comments |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This change switches the MigrationManager to use the UsedResourcesMap This allows it to support parallel manual migrations. |
| Comment by Githook User [ 03/Aug/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This change exposes the lock/unlock methods as public on the Also makes the sharding balancer acquire the balancer distributed lock |