[
https://issues.apache.org/jira/browse/CASSANDRA-16869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401786#comment-17401786
]
Josh McKenzie commented on CASSANDRA-16869:
-------------------------------------------
Tests are in flight after tidying up a couple failures.
||Item||Link||
|j8
test|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/49/workflows/edbc5e1c-87f5-4a67-89d6-34520b337326]|
|j11
test|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/49/workflows/891ad9d2-1375-4c17-b8fc-e2a7a9c69b50]|
|branch|[link|https://github.com/apache/cassandra/compare/cassandra-4.0...josh-mckenzie:repair_log_exceptions?expand=1]|
> Reduce the amount of logging on "expected" repair exceptions
> ------------------------------------------------------------
>
> Key: CASSANDRA-16869
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16869
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
>
> Many of the repair errors we throw in the logs are redundant. For example, if
> one node has an unreadable sstable, we should log that at ERROR, but then the
> failing repairs due to that unreadable sstable should be at WARN, making it
> easier to find and debug the actual problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
