[SERVER-27923] Balancer get stuck for unresponsive server Created: 06/Feb/17  Updated: 27/Oct/23  Resolved: 07/Feb/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.0.14, 3.2.12
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Gilad W Assignee: Kelsey Schubert
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

Created 2 mongos on different servers on a sharding cluster.
Wait for the mongos to get balancer lock while doing "doing balance round" then shutdown the mongos server.

Participants:

 Description   

I have application mongos on many servers. when the server of balancer gets shut down, the whole process gets stopped and no new balancer is getting selected.

This problem can be solve by also allowing to choose the specific possible balancers hosts it would solve the problem.

From today:
db.locks.findOne({_id:"balancer"})

{ "_id" : "balancer", "state" : 2, "ts" : ObjectId("588a11a3e39015c05a6bd2da"), "who" : "ip-10-50-80-254:27018:1485443270:-728686220:Balancer", "process" : "ip-10-50-80-254:27018:1485443270:-728686220", "when" : ISODate("2017-01-26T15:11:31.774Z"), "why" : "doing balance round" }

 Comments   
Comment by Kelsey Schubert [ 07/Feb/17 ]

Hi giladw@mintigo.com,

Thanks for the report. This issue has been resolved in MongoDB 3.4 as the balancer only runs on the primary config server.

If this is an issue for you, I would recommend upgrading to MongoDB 3.4.2.

Kind regards,
Thomas

Generated at Thu Feb 08 04:16:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.