[
https://issues.apache.org/jira/browse/CASSANDRA-15661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068580#comment-17068580
]
Alexander Dejanovski commented on CASSANDRA-15661:
--------------------------------------------------
[~rustyrazorblade], I'm overall super happy to get more loggings back in
system.log.
Having all of what's happening in flushes and compactions at debug level made
my life as an ops much harder over the past years.
I added a few comments on the PR regarding some that may not be fit for INFO
level. They look more like ways to actually debug some implementation details
around repair.
Let me know what you think.
> 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
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
