[
https://issues.apache.org/jira/browse/CASSANDRA-14326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406317#comment-16406317
]
Paulo Motta commented on CASSANDRA-14326:
-----------------------------------------
I think we should go with 2 otherwise we lose the ability introduced by
CASSANDRA-10421 to have a human-readable system.log vs verbose troubleshooting
log, which I think it has been useful to troubleshoot hard-to-reproduce issues
after the fact without affecting performance (best-effort async-appender
logging) and cluttering system.log readability (separation of system vs debug
log), but I'd be interested in hearing more on what operators from 3.0+
clusters think of the current separation of system.log and debug.log.
In any case, the first step of this ticket is to go through all messages being
logged at DEBUG and reclassify important ones as INFO, and then we can decide
to go with 1 or 2 later.
> 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.0
>
>
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
