cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Dejanovski (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-14326) Handle verbose logging at a different level than DEBUG
Date Tue, 20 Mar 2018 07:41:00 GMT
Alexander Dejanovski created CASSANDRA-14326:
------------------------------------------------

             Summary: 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
             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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message