[ https://issues.apache.org/jira/browse/CASSANDRA-15661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Haddad updated CASSANDRA-15661: ----------------------------------- Fix Version/s: 4.0-alpha Source Control Link: https://github.com/apache/cassandra/commit/dd9a6e0a8a691bdee357eb6559f1b2b92b076925 Resolution: Fixed Status: Resolved (was: Ready to Commit) > 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 > Fix For: 4.0-alpha > > Time Spent: 2h 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