[SERVER-4282] clean up log messages Created: 15/Nov/11  Updated: 03/Jan/18  Resolved: 08/Jul/14

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 2.0.1
Fix Version/s: 2.7.4

Type: Improvement Priority: Minor - P4
Reporter: Daniel Pasette (Inactive) Assignee: Benety Goh
Resolution: Done Votes: 16
Labels: polish
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-5092 Better named logging with tracing Closed
Related
related to SERVER-4780 Improve Memory Leak Warning Message Closed
is related to SERVER-13922 remove dbtemprelease Closed
is related to SERVER-3989 Cannot suppress ClientCursor::yield "... Closed
Sprint: Server 2.7.4
Participants:
Case:

 Description   

We need to clean up our log messages. We generate a lot of noise because many log messages are not actionable, and don't mean anything – they appear to have been put in for original development and debugging, and left there. One example I get asked about a lot is the warning about being unable to release a recursive lock from a mapreduce.



 Comments   
Comment by Benety Goh [ 08/Jul/14 ]

Fine-grained logging for debug messages was introduced in SERVER-5092.

Logging API cleanup work in SERVER-14111, SERVER-14112, SERVER-14113, SERVER-14114 and SERVER-14116 went into 2.7.2.

Comment by Benety Goh [ 08/Jul/14 ]

Recursive lock warnings were removed in SERVER-13922

Comment by Benson Margulies [ 08/Mar/13 ]

It's not just mapreduce. Recursive log messages can occur from findandmodify queries:

Fri Mar 8 16:03:56 [conn20] warning: ClientCursor::yield can't unlock b/c of recursive lock ns: juggernaut.documents top: { opid: 14656, active: true, secs_running: 0, op: "query", ns: "juggernaut", query: { findandmodify: "documents", query:
{ blobs.index.state: null, blobs.text.state: "DONE", blobs.analysis.state: "DONE", blobs.classification.state: "DONE", blobs.coref.state: "DONE" }
, fields:
{ _id: 1, documentId: 1, created: 1, metadata: 1, blobs.text: 1, blobs.analysis: 1, blobs.classification: 1, blobs.coref: 1 }
, sort:
{ blobs.coref.timestamp: 1 }
, update: { $set: { blobs.index:
{ state: "PENDING", timestamp: new Date(1362776636301) }
} }, new: true }, client: "127.0.0.1:62285", desc: "conn20", threadId: "0x128187000", connectionId: 20, locks:
{ ^: "w", ^juggernaut: "W" }
, waitingForLock: false, numYields: 0, lockStats: { timeLockedMicros: {}, timeAcquiringMicros:
{ r: 0, w: 3 }
} }

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