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

balancer locked in state 0

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.2.1
    • Sharding
    • None
    • ubuntu 12.04.01 LTS
    • Linux
    • Hide

      above is the information from the mongos log when the lock was acquired and the output of the mongos locks.

      Show
      above is the information from the mongos log when the lock was acquired and the output of the mongos locks.

    Description

      Balancer seems to have gotten stuck after acquiring a lock which then stopped all balancing until we logged into the mongos and stop/started the balancer.

      mongos log-
      Fri Jan 18 00:45:02 [Balancer] distributed lock 'balancer/ms-db-4:27017:1354112926:1804289383' acquired, ts : 50f8fd7e8d5ca2b8deff6383

      use config;
      mongos> db.locks.find(

      { _id : "balancer" }

      ).pretty()
      {
      "_id" : "balancer",
      "process" : "ms-db-4:27017:1354112926:1804289383",
      "state" : 0,
      "ts" : ObjectId("50f8fd7e8d5ca2b8deff6383"),
      "when" : ISODate("2013-01-18T07:45:02.249Z"),
      "who" : "ms-db-4:27017:1354112926:1804289383:Balancer:846930886",
      "why" : "doing balance round"
      }

      we didn't notice this until today that we had no balancing happening.

      Attachments

        1. mlog
          6 kB
        2. o
          8 kB

        Activity

          People

            andre.defrere@mongodb.com Andre de Frere
            joep joe piscitella
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: