[SERVER-21776] Move per-operation log lines for queries out of the QUERY log component Created: 04/Dec/15  Updated: 18/Nov/16  Resolved: 05/Jan/16

Status: Closed
Project: Core Server
Component/s: Logging, Querying
Affects Version/s: None
Fix Version/s: 3.0.9, 3.2.3, 3.3.1

Type: Improvement Priority: Major - P3
Reporter: David Storch Assignee: J Rassi
Resolution: Done Votes: 0
Labels: code-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-7006 Document that the slow operation log ... Closed
Related
related to SERVER-22745 refine "command" log component into s... Backlog
is related to SERVER-21769 Find, getMore, and killCursors comman... Closed
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: QuInt E (01/11/16)
Participants:

 Description   

In order to diagnose query engine-related problems, we would often like users to enable logLevel 1 specifically for the QUERY log component. However, this also causes every query operation to generate a log line. This is much too verbose for many users, which makes collecting query-related diagnostics impossible. In order to fix this, we should consider moving the per-operation debug lines to either an existing log component (kDefault? kCommand?) or a new log component.



 Comments   
Comment by Githook User [ 20/Jan/16 ]

Author:

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

Message: SERVER-21776 Diagnostic logic for reads/writes should use correct log component

(cherry picked from commit f210ee304a3b6eeb85a67305e6a97a32e1df3c81)
Branch: v3.0
https://github.com/mongodb/mongo/commit/20d60d3491908f1ae252fe452300de3978a040c7

Comment by Githook User [ 20/Jan/16 ]

Author:

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

Message: SERVER-21776 Diagnostic logic for reads/writes should use correct log component

(cherry picked from commit f210ee304a3b6eeb85a67305e6a97a32e1df3c81)
Branch: v3.2
https://github.com/mongodb/mongo/commit/f0df9f46e6979af1bd922c8ee36c2c35f722b400

Comment by Githook User [ 20/Jan/16 ]

Author:

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

Message: SERVER-21776 Diagnostic logic for reads/writes should use correct log component
Branch: master
https://github.com/mongodb/mongo/commit/f210ee304a3b6eeb85a67305e6a97a32e1df3c81

Comment by Githook User [ 12/Jan/16 ]

Author:

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

Message: SERVER-21776 CachedPlanStage: add post-replan log msgs at log level 1

(cherry picked from commit 3372811fc15df4592515a57b1cfdbaed2b703735)
Branch: v3.2
https://github.com/mongodb/mongo/commit/c49d0b2c997d85b82be934dd3d9397ab6850f6a0

Comment by Githook User [ 12/Jan/16 ]

Author:

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

Message: SERVER-21776 Most instance.cpp log msgs should use kCommand component

(cherry picked from commit 7834ab9782d90b82ff023c5c886635962e8d5417)
Branch: v3.2
https://github.com/mongodb/mongo/commit/d9e55e98975a077fa815afb19c5abd2d5e75d395

Comment by Githook User [ 07/Jan/16 ]

Author:

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

Message: SERVER-21776 CachedPlanStage: add post-replan log msgs at log level 1

(cherry picked from commit 3372811fc15df4592515a57b1cfdbaed2b703735)
Branch: v3.0
https://github.com/mongodb/mongo/commit/1aae0bbeb1d9c0b6a973076acba398ac1b65d0fc

Comment by Githook User [ 07/Jan/16 ]

Author:

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

Message: SERVER-21776 Most instance.cpp log msgs should use kCommand component

(cherry picked from commit 7834ab9782d90b82ff023c5c886635962e8d5417)
Branch: v3.0
https://github.com/mongodb/mongo/commit/4d33d81c789ad99cbc5204c20ebb0cadb7bc2b95

Comment by Githook User [ 05/Jan/16 ]

Author:

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

Message: SERVER-21776 CachedPlanStage: add post-replan log msgs at log level 1
Branch: master
https://github.com/mongodb/mongo/commit/3372811fc15df4592515a57b1cfdbaed2b703735

Comment by Githook User [ 30/Dec/15 ]

Author:

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

Message: SERVER-21776 Most instance.cpp log msgs should use kCommand component
Branch: master
https://github.com/mongodb/mongo/commit/7834ab9782d90b82ff023c5c886635962e8d5417

Comment by Daniel Pasette (Inactive) [ 06/Dec/15 ]

We really need to do a holistic re-jiggering of our log levels and components. We need to start with developer guidelines for which level is appropriate for which sort of information. I understand the problem here though, so I'm not opposed to a short term fix, but I'd like to see a bit more fleshed out proposal.

Comment by David Storch [ 04/Dec/15 ]

dan@10gen.com, I think this will be very useful for diagnosing plan selection problems on 3.0 and 3.2 going forward. We have logging for when replanning kicks in which may give us a picture of how we end up with slow queries.

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