[SERVER-26014] ReplsetDistLockManager logging garbage string. Created: 07/Sep/16  Updated: 05/Apr/17  Resolved: 08/Sep/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File logs.txt    
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 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



 Comments   
Comment by Dianna Hohensee (Inactive) [ 08/Sep/16 ]

Looks like it is just the fuzzer providing crazy collection names.

The code thinks that that's the collection name, not garbage.

{ findAndModify: "locks", query: { ts: ObjectId('57d04fffbc903c70af6be536'), _id: "����������������" }, update: { $set: { state: 0 } }, writeConcern: { w: "majority", wtimeout: 15000 }, maxTimeMS: 30000 }

Closing.

Comment by Andy Schwerin [ 08/Sep/16 ]

dianna.hohensee, check to see if that's just the collection name the fuzzer supplied.

Generated at Thu Feb 08 04:10:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.