[SERVER-31075] Balancer is running but it's disabled Created: 13/Sep/17 Updated: 27/Oct/23 Resolved: 14/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kay Agahd | Assignee: | Mark Agarunov |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
The balancer is running even though it's disabled:
In config.locks there is a balancer entry:
We restarted all routers (mongos) and configservers but the balancer is still running. Btw. the dbs is not yet in use and therefore nearly empty since it's not yet in production.
|
| Comments |
| Comment by Kaloian Manassiev [ 14/Sep/17 ] | ||||||||
|
Thanks for confirming, kay.agahd@idealo.de! Just for posterity, this is the documentation link, which explains the 3.4 behaviour change: https://docs.mongodb.com/manual/tutorial/manage-sharded-cluster-balancer/#check-if-balancer-is-running | ||||||||
| Comment by Kay Agahd [ 14/Sep/17 ] | ||||||||
|
that's it, you're right! We were using a mongo shell v3.2. Using mongo shell v3.4 correctly shows that the balancer is stopped:
You may close this ticket as resolved. Thanks! | ||||||||
| Comment by Kaloian Manassiev [ 14/Sep/17 ] | ||||||||
|
Can you please confirm whether you are running version 3.4 of the mongo shell to run these commands? In MongoDB 3.4 we moved the balancer to run on the CSRS config server's primary and as a result it now permanently holds the balancer lock in order to prevent any accidentally left 3.2 or prior mongos instances for doing balancing. Because of this, all functions from shells before 3.4, which rely on the status of the balancer lock, no longer work. Instead, we introduced a new command. Best regards, | ||||||||
| Comment by Kay Agahd [ 14/Sep/17 ] | ||||||||
|
Hello mark.agarunov, I tried to upload the log files without success
Could you provide us a non-public upload location please? We generally keep our log files for only 7 days so probably the log file containing the cause has been rotated already. | ||||||||
| Comment by Mark Agarunov [ 13/Sep/17 ] | ||||||||
|
Hello kay.agahd@idealo.de, Thank you for the report. It seems from the output that there may be a lock that has not been relinquished from a previous run of the balancer. To get a better idea of what may be causing this, could you please provide the logs from all affected mongos and mongod nodes? Thanks, | ||||||||
| Comment by Kay Agahd [ 13/Sep/17 ] | ||||||||
|
Also quite weird:
|