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

ReplsetDistLockManager logging garbage string.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL

    Description

      DistLockManager is somehow writing some garbage from a string rather than actual info. Causing no evident harm, just bad logging.

      https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_windows_64_jstestfuzz_sharded_b5277068ff66e7fe2b2a98144aa6993ca6e17f5c_16_09_07_15_31_44

      "[ShardedClusterFixture:job0:mongos] 2016-09-07T18:00:16.598+0000 W SHARDING [replSetDistLockPinger] Failed to unlock lock with ts: 57d04fffbc903c70af6be536 and _id: ���������������:5 :: caused by :: ExceededTimeLimit: Operation timed out, request was RemoteCommand 6087 -- target:WIN-DE8E6H6F6GH:20000 db:config expDate:2016-09-07T18:00:16.597+0000 cmd:{ findAndModify: "locks", query: { ts: ObjectId('57d04fffbc903c70af6be536'), _id: "�"
      

      Logging is coming from here: https://github.com/mongodb/mongo/blob/5133e213c79378893f6bc7671e57789e1f6a9874/src/mongo/s/catalog/replset/replset_dist_lock_manager.cpp#L162-L163

      Attachments

        1. logs.txt
          2.58 MB

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: