Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-31075

Balancer is running but it's disabled

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.6
    • Component/s: Sharding
    • None
    • ALL

      The balancer is running even though it's disabled:

      mongos> sh.getBalancerState()
      false
      mongos> sh.isBalancerRunning()
      true
      

      In config.locks there is a balancer entry:

      mongos> db.locks.find({_id:"balancer"})
      { "_id" : "balancer", "state" : 2, "ts" : ObjectId("59b93d04d035a79b193cea5b"), "who" : "ConfigServer:Balancer", "process" : "ConfigServer", "when" : ISODate("2017-09-13T14:13:37.034Z"), "why" : "CSRS Balancer" }

      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.

      mongos> show dbs
      admin   0.000GB
      config  0.007GB
      mongos> sh.status()
      --- Sharding Status ---
        sharding version: {
      	"_id" : 1,
      	"minCompatibleVersion" : 5,
      	"currentVersion" : 6,
      	"clusterId" : ObjectId("598ab847e97e92ba40fa56ee")
      }
        shards:
      	{  "_id" : "offerHistory01",  "host" : "offerHistory01/mongo-016.db00.pro06.eu.idealo.com:27017,mongo-105.db00.pro05.eu.idealo.com:27017",  "state" : 1 }
      	{  "_id" : "offerHistory02",  "host" : "offerHistory02/mongo-119.db00.pro06.eu.idealo.com:27017,mongo-120.db00.pro06.eu.idealo.com:27017",  "state" : 1 }
      	{  "_id" : "offerHistory03",  "host" : "offerHistory03/mongo-121.db00.pro06.eu.idealo.com:27017,mongo-122.db00.pro06.eu.idealo.com:27017",  "state" : 1 }
      	{  "_id" : "offerHistory04",  "host" : "offerHistory04/mongo-047.db00.pro06.eu.idealo.com:27017,mongo-123.db00.pro06.eu.idealo.com:27017",  "state" : 1 }
        active mongoses:
      	"3.4.6" : 5
        balancer:
      	Currently enabled:  no
      	Currently running:  yes
      		Balancer lock taken at Wed Sep 13 2017 16:13:37 GMT+0200 (CEST) by ConfigServer:Balancer
      	Failed balancer rounds in last 5 attempts:  5
      	Last reported error:  Cannot accept sharding commands if not started with --shardsvr
      	Time of Reported error:  Fri Aug 25 2017 08:46:00 GMT+0200 (CEST)
      	Migration Results for the last 24 hours:
      		3 : Success
        databases:
      mongos>
      

            Assignee:
            mark.agarunov Mark Agarunov
            Reporter:
            kay.agahd@idealo.de Kay Agahd
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: