[
https://issues.apache.org/jira/browse/CASSANDRA-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743886#comment-14743886
]
Robert Coli commented on CASSANDRA-10241:
-----------------------------------------
Thanks [~jbellis] for the ping.
I am pretty strongly +1 on a default DEBUG level log that is always enabled.
Users seeking support on #cassandra/(-user@) frequently don't find out about an
issue until after it has happened. When they do find out about it, I'd love to
be able to tell them what classes to enable at DEBUG level. Unfortunately, I
have serious FUD about accidentally instructing them to enable DEBUG on some
set of classes which will render the resulting log spammy and useless. If I
were able to direct them to a log that was reasonably sized and contained the
last two weeks or so of relevant DEBUG information, the quality and
actionability of bug reports would increase significantly.
As to an approach, knocking all current DEBUG to TRACE seems reasonable on its
face. "We" should opt log messages in to the new-very-useful-DEBUG-log, not opt
them out.
I agree with jeffj's sentiments about a handle to disable such logging, but I
find that in practice concerns about logging overhead are often over-estimated.
For example, the CPU/io/etc. overhead of enabling the full query log on one of
my high throughput production MySQL slaves (which is more analogous to the more
heavyweight "read/write path DEBUG logging") is not significant versus other
impacts on my system graphs. The meaningful problem in that case is that the
log is writing to a disk of finite size.. :)
> Keep a separate production debug log for troubleshooting
> --------------------------------------------------------
>
> Key: CASSANDRA-10241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10241
> Project: Cassandra
> Issue Type: New Feature
> Components: Config
> Reporter: Jonathan Ellis
> Assignee: Paulo Motta
> Fix For: 2.1.x, 2.2.x, 3.0.x
>
>
> [~aweisberg] had the suggestion to keep a separate debug log for aid in
> troubleshooting, not intended for regular human consumption but where we can
> log things that might help if something goes wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
