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

dist_lock cleanup failed, invalid BSONObj 0xEEEEEEEE

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 1.8.3
    • None
    • None
    • Ubuntu

    Description

      We're getting an error on all of our mongos processes for one of our DBs:

      Thu Feb 23 10:06:02 [LockPinger] warning: dist_lock cleanup request from process: monitor01:1330020332:1804289383 to: mongoconfig01:27017,mongoconfig02:27017,mongoconfig03:27017 failed: Invalid BSONObj size: -286331154 (0xEEEEEEEE) first element: _id: "monitor01:1320796130:1804289383"

      We see the same error in different forms on other app servers:

      Thu Feb 23 10:18:05 [LockPinger] warning: dist_lock cleanup request from process: app01:1325044333:1804289383 to: mongoconfig01:27017,mongoconfig02:27017,mongoconfig03:27017 failed: Invalid BSONObj size: -286331154 (0xEEEEEEEE) first element: _id: "monitor01:1320796130:1804289383"

      This looks like something is corrupt in the distributed locking, and "monitor01:1320796130:1804289383" is failing to update. If we've restarted the mongos on monitor01, is there a way to manually clean that up, or to have mongo automatically fix that?

      Attachments

        Activity

          People

            scotthernandez Scott Hernandez (Inactive)
            siteops@reputation.com Site Operations
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: