[SERVER-24782] Make the sharding balancer thread always be active on the primary Created: 24/Jun/16 Updated: 18/Aug/16 Resolved: 29/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.10 |
| Type: | Bug | 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 |
| Operating System: | ALL |
| Sprint: | Sharding 17 (07/15/16) |
| Participants: |
| Description |
|
Currently, the sharding balancer thread is stopped when the controlBalancer: stop command is run and it won't be restarted if just the balancer document is set to enabled. However, if a step-down happens, that thread will be restarted but it won't do anything. This makes it slightly asymetric so we should make the thread always run. |
| Comments |
| Comment by Githook User [ 29/Jun/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This change gets rid of the serverStatus.balancer section and moves its In addition it gets rid of the 'controlBalancer' command and splits it |