[
https://issues.apache.org/jira/browse/CASSANDRA-15661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067835#comment-17067835
]
Jon Haddad commented on CASSANDRA-15661:
----------------------------------------
I'll have Jenkins test results here as soon as I'm able to run unit + dtests.
ATM the new jenkins setup is failing my builds and CircleCI bombs out when
running dtests on medium instances. I can't think of a reason why unit tests
would break, but dtests might be relying on logs at a specific level.
Hopefully I can get the CI results posted today.
> 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: 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
