[jira] [Updated] (CASSANDRA-15661) Improve logging by using more appropriate levels

["Jon Haddad (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-15661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Haddad updated CASSANDRA-15661:
-----------------------------------
    Change Category: Operability
         Complexity: Low Hanging Fruit
             Status: Open  (was: Triage Needed)

>  Improve logging by using more appropriate levels
> -------------------------------------------------
>
>                 Key: CASSANDRA-15661
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15661
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability/Logging
>            Reporter: Jon Haddad
>            Assignee: Jon Haddad
>            Priority: Normal
>
> There are a number of log statements using logging levels that are a bit too conservative.  For example:
> * Flushing memtables is currently at debug.  This is a relatively rare event that is important enough to be INFO
> * When compaction finishes we log the progress at debug
> * Different steps in incremental repair are logged as debug, should be INFO
> * when reaching connection limits in ConnectionLimitHandler.java we log at warn rather than error.  Since this is a client disconnect it’s more than a warning, we’re taking action and disconnecting.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org