You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (JIRA)" <ji...@apache.org> on 2018/03/20 14:15:00 UTC
[jira] [Comment Edited] (CASSANDRA-14326) Handle verbose logging at
a different level than DEBUG
[ https://issues.apache.org/jira/browse/CASSANDRA-14326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406387#comment-16406387 ]
Paulo Motta edited comment on CASSANDRA-14326 at 3/20/18 2:14 PM:
------------------------------------------------------------------
bq. The only thing I can think of that will be a bit odd, is to have two different logs, both having INFO messages with one being a superset of the other.
We could add a new marker INFO-VERBOSE, that is logged asynchronously to verbose-system.log (former debug.log) - all other INFO/WARN/ERROR logs would only go to system.log. Admins would typically only look at system.log, and only go to verbose-system.log when facing problems, troubleshooting issues or wanting to perform advanced tuning, etc. Ultimately advanced operators could still disable the system-verbose.log if/when they're not interested in that.
was (Author: pauloricardomg):
bq. The only thing I can think of that will be a bit odd, is to have two different logs, both having INFO messages with one being a superset of the other.
We could add a new marker INFO-VERBOSE, that is logged asynchronously to verbose-system.log (former debug.log). Admins would typically only look at system.log, and only go to verbose-system.log when facing problems, troubleshooting issues or wanting to perform advanced tuning, etc. Ultimately advanced operators could still disable the system-verbose.log if/when they're not interested in that.
> Handle verbose logging at a different level than DEBUG
> ------------------------------------------------------
>
> Key: CASSANDRA-14326
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14326
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Alexander Dejanovski
> Priority: Major
> Fix For: 4.x
>
>
> CASSANDRA-10241 introduced debug logging turned on by default to act as a verbose system.log and help troubleshoot production issues.
> One of the consequence was to severely affect read performance in 2.2 as contributors weren't all up to speed on how to use logging levels (CASSANDRA-14318).
> As DEBUG level has a very specific meaning in dev, it is confusing to use it for always on verbose logging and should probably not be used this way in Cassandra.
> Options so far are :
> # Bring back common loggings to INFO level (compactions, flushes, etc...) and disable debug logging by default
> # Use files named as verbose-system.log instead of debug.log and use a custom logging level instead of DEBUG for verbose tracing, that would be enabled by default. Debug logging would still exist and be disabled by default and the root logger level (not just filtered at the appender level).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org