[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: |
|
||||||||||||||||||||
| 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: (cherry picked from commit f210ee304a3b6eeb85a67305e6a97a32e1df3c81) |
| Comment by Githook User [ 20/Jan/16 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: (cherry picked from commit f210ee304a3b6eeb85a67305e6a97a32e1df3c81) |
| Comment by Githook User [ 20/Jan/16 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |
| Comment by Githook User [ 12/Jan/16 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: (cherry picked from commit 3372811fc15df4592515a57b1cfdbaed2b703735) |
| Comment by Githook User [ 12/Jan/16 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: (cherry picked from commit 7834ab9782d90b82ff023c5c886635962e8d5417) |
| Comment by Githook User [ 07/Jan/16 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: (cherry picked from commit 3372811fc15df4592515a57b1cfdbaed2b703735) |
| Comment by Githook User [ 07/Jan/16 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: (cherry picked from commit 7834ab9782d90b82ff023c5c886635962e8d5417) |
| Comment by Githook User [ 05/Jan/16 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |
| Comment by Githook User [ 30/Dec/15 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |
| 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. |