-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.2.3
-
Component/s: Sharding
-
None
-
Linux
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
We have a sharded cluster of 2.2.3 version of mongo. We are going to upgrade it to 2.4.12, but faced an issue when we cannot stop the balancer (in fact we hoped it was already stopped).
So, connection to one of /mongos/ shows us:
mongos> sh.isBalancerRunning() true mongos> sh.getBalancerState() false mongos> use config switched to db config mongos> db.locks.find({'_id': 'balancer'}).pretty() { "_id" : "balancer", "process" : "atc005:37017:1415292838:1804289383", "state" : 1, "ts" : ObjectId("5485b6e0903bf7e88aaa2276"), "when" : ISODate("2014-12-08T14:34:08.769Z"), "who" : "atc005:37017:1415292838:1804289383:Balancer:1169620192", "why" : "doing balance round" } mongos> sh.stopBalancer() Waiting for active hosts... Waiting for the balancer lock...
sh.stopBalancer() takes forever. The situation is very similar to SERVER-7260 but the author of the previous ticket disappeared.
I wonder if we can forcefully remove that lock?