[SERVER-6285] Lock reporting in slow query log messages isn't reset after each operation Created: 03/Jul/12  Updated: 11/Jul/16  Resolved: 03/Jul/12

Status: Closed
Project: Core Server
Component/s: Concurrency, Logging
Affects Version/s: 2.1.2
Fix Version/s: 2.2.0-rc0

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

Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

Example output:

Sun Jul  1 00:05:06 [conn42] insert fooasdf.bar keyUpdates:0 locks(micros) R:115904 r:7 w:43892834 300ms
Sun Jul  1 00:05:08 [conn42] insert fooasdf.bar keyUpdates:0 locks(micros) R:115904 r:7 w:44697906 105ms
Sun Jul  1 00:05:12 [conn42] insert fooasdf.bar keyUpdates:0 locks(micros) R:115904 r:7 w:47557207 103ms
Sun Jul  1 00:05:15 [conn42] insert fooasdf.bar keyUpdates:0 locks(micros) R:115904 r:7 w:49683582 136ms
Sun Jul  1 00:05:21 [conn42] insert fooasdf.bar keyUpdates:0 locks(micros) R:115904 r:7 w:53233815 109ms
Sun Jul  1 00:05:22 [conn42] insert fooasdf.bar keyUpdates:0 locks(micros) R:115904 r:7 w:54007353 599ms



 Comments   
Comment by auto [ 03/Jul/12 ]

Author:

{u'date': u'2012-07-03T01:15:42-07:00', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-6285 - reset lock stats in CurOp when a new request starts
Branch: master
https://github.com/mongodb/mongo/commit/825da30c930a7e8b824bcc355fe1564f278ca7ba

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