[DOCS-8140] Document the new balancer control commands and the deprecation of the old shell's balancer control scripts Created: 21/Jun/16 Updated: 04/Mar/23 Resolved: 28/Nov/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0, mongodb-3.4p1, DOCS Q3 W10, DOCS Q3 W10-part_deux |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Kaloian Manassiev | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 7 years, 11 weeks, 2 days ago | ||||||||||||||||
| Epic Link: | 3.4: Sharding Updates | ||||||||||||||||
| Story Points: | 1.5 | ||||||||||||||||
| Description |
|
Prior to v3.4, the start/stopBalancer shell scripts were using the config.settings section plus the state of the balancer lock in order to set the balancer state. In sharding 3.4, the balancer is running on the CSRS primary and it permanently holds the balancer lock in order to prevent any legacy 3.2 mongos instance from attempting to do balancing. Since the old shell scripts for start/stopBalancer relied on the state of the balancer lock to determine whether it is running, with this change these old scripts no longer work. The new way to interact with the balancer in 3.4 is through the startBalancer/stopBalancer/balancerStatus commands. The way they work is:
Backwards compatibility The 3.4 shell is backwards compatible with sharded clusters, which are running all components on 3.2 or earlier (config, shards and mongos). The 3.2 and earlier shell is not compatible with 3.4 clusters. For clusters which are in the process of being upgraded, the following rules apply: If only the CSRS config server primary has been upgraded to 3.4, but not the shards and mongos, neither the old shell balancer control will work, nor the 3.4 one. In order to be able to control the balancer in this state, a one-off mongos instance needs to be spawned so the balancer control commands are available. |
| Comments |
| Comment by Githook User [ 28/Nov/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Kay Kim (Inactive) [ 14/Oct/16 ] |
|
I think we might have been looking at the wrong SERVER ticket. I believe the main SERVER ticket for this is indeed fixed and going. The ticket you were looking at – that is an effect cc: emily.hall |
| Comment by Emily Hall [ 28/Sep/16 ] |
|
Closing issue because linked Server ticket was resolved as "Won't Fix" |