0

I have upgrade 3 months ago a mongoDB sharded cluster from 2.4.9 to 2.6.1 . I haven't faced any issues with the upgrade and my cluster working fine, but i still see the initial lock that required to update metadata to v5 on my config servers.

     "_id" : "configUpgrade",
    "process" : "pgdb2:27017:1399361525:1804289383",
    "state" : 0,
    "ts" : ObjectId("53688ff569fb6f34e9a2d398"),
    "when" : ISODate("2014-05-06T07:32:05.343Z"),
    "who" : "pgdb2:27017:1399361525:1804289383:mongosMain:846930886",
    "why" : "upgrading config database to new format v5"

Does anybody knows if this is bug or if it is going to affect any future operation?

  • Have you followed docs.mongodb.org/manual/release-notes/2.6-upgrade by the letters? – Markus W Mahlberg Sep 15 '14 at 10:21
  • @MarkusWMahlberg: Yes, the weird is that temp mongos i used for upgrade meta-data seems to release the lock 2014-05-06T10:32:05.702+0300 [mongosMain] distributed lock 'configUpgrade/pgdb2:27017:1399361525:1804289383' unlocked. – Antonios Sep 15 '14 at 11:32
  • 1
    The upgrade lock record is not removed post upgrade. The "state" of 0 means the lock is not being held. You can ignore or remove manually. – James Wahlin Sep 15 '14 at 13:06
  • Thanks @JamesWahlin , is there any document that describes lock states? – Antonios Sep 15 '14 at 13:09
  • I have not found documentation but there is a comment in the 2.6 code detailing: github.com/mongodb/mongo/blob/v2.6/src/mongo/s/… – James Wahlin Sep 15 '14 at 13:25
1

The upgrade lock record is not removed post upgrade. A "state" of 0 means the lock is not being held. You can ignore or remove manually.

The lock definitions for MongoDB 2.6 are available here and are:

0: Unlocked | 1: Locks in contention | 2: Lock held

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.