[
https://issues.apache.org/jira/browse/CASSANDRA-15661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072240#comment-17072240
]
Jon Haddad commented on CASSANDRA-15661:
----------------------------------------
Got my circle ci results.
[Unit
tests|https://app.circleci.com/pipelines/github/rustyrazorblade/cassandra/17/workflows/82684478-5d63-4ab2-8db4-b6c05d05edca/jobs/236]
passing
[JVM
DTest|https://app.circleci.com/pipelines/github/rustyrazorblade/cassandra/17/workflows/82684478-5d63-4ab2-8db4-b6c05d05edca/jobs/235]
passing
[DTests|https://app.circleci.com/pipelines/github/rustyrazorblade/cassandra/17/workflows/82684478-5d63-4ab2-8db4-b6c05d05edca/jobs/237]
have a single failure that appears to be unrelated (failure with repair due to
a node not starting)
> 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: 2h 10m
> 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: [email protected]
For additional commands, e-mail: [email protected]
