[SERVER-17699] "locks" section empty in diagnostic log and profiler output for some operations Created: 23/Mar/15  Updated: 19/Sep/15  Resolved: 24/Mar/15

Status: Closed
Project: Core Server
Component/s: Diagnostics, Storage
Affects Version/s: 3.0.0
Fix Version/s: 3.0.2, 3.1.1

Type: Bug Priority: Major - P3
Reporter: J Rassi Assignee: J Rassi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Quint Iteration 3.1.1
Participants:

 Description   

The "locks" section in the diagnostic log and profiler output is empty for some operations, including basic reads.

Example diagnostic log output exhibiting the problem (note "locks:{}" towards the end of the log line):

2015-03-23T13:09:52.633-0400 I QUERY    [conn1] query test.foo planSummary: COLLSCAN cursorid:36168749481 ntoreturn:0 ntoskip:0 nscanned:0 nscannedObjects:101 keyUpdates:0 writeConflicts:0 numYields:0 nreturned:101 reslen:2253 locks:{} 0ms



 Comments   
Comment by Githook User [ 26/Mar/15 ]

Author:

{u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}

Message: SERVER-17699 LockerImpl<>::getLockerInfo() don't no-op if not locked

(cherry picked from commit d5f0d74d5c4a75a74e1d506ba224e54ee57f9a0b)
Branch: v3.0
https://github.com/mongodb/mongo/commit/262e2a95fb8b880ff8f03d68774174da544d71d3

Comment by Githook User [ 24/Mar/15 ]

Author:

{u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}

Message: SERVER-17699 LockerImpl<>::getLockerInfo() don't no-op if not locked
Branch: master
https://github.com/mongodb/mongo/commit/d5f0d74d5c4a75a74e1d506ba224e54ee57f9a0b

Generated at Thu Feb 08 03:45:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.