[SERVER-24721] Make BalancerPolicy::balance return more than one migration per collection (if appropriate) Created: 22/Jun/16 Updated: 19/Jul/16 Resolved: 14/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.10 |
| 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 17 (07/15/16) |
| Participants: |
| Description |
|
Currently, the BalancerPolicy::balance call, which is used by the sharding balancer returns a single migration per collection. In order to better utilize the ability to move multiple chunks in parallel across the cluster, this call should be made to return more than one migration per collection if this is appropriate. For example:
Care should be taken that the balancer does not move chunks over-zealously and cause unnecessary churn in the cluster. |
| Comments |
| Comment by Githook User [ 17/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 14/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This change makes the BalancerPolicy return multiple migrations per These migrations are still executed serially. |
| Comment by Githook User [ 14/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: The collection DistributionStatus class shouldn't contain information |
| Comment by Githook User [ 12/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |