[
https://issues.apache.org/jira/browse/CASSANDRA-16869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-16869:
--------------------------------------
Resolution: Duplicate
Status: Resolved (was: Open)
Thanks for the review [~jmeredithco] - I spaced on this one and it's a 4.0.x
dupe version of what Caleb did on trunk (that, ironically and slightly
horrifically, _I reviewed_ a month ago) on CASSANDRA-16775. I kept trying to
figure out why it felt so familiar...
I'm going to blame this on the time dilation effect of 2020/2021 and close as
dupe, though I will pursue us getting the RepairErrorsTest into the 4.0.x line.
No harm in having more testing in the patch line.
> 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
> Fix For: 4.0.x
>
>
> 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]
