[
https://issues.apache.org/jira/browse/CASSANDRA-16209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213480#comment-17213480
]
Caleb Rackliffe edited comment on CASSANDRA-16209 at 10/14/20, 2:38 PM:
------------------------------------------------------------------------
[patch|https://github.com/apache/cassandra/pull/776]
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-16209]
Note: The failures in the first round of tests look mostly related to
CASSANDRA-16148
was (Author: maedhroz):
[patch|https://github.com/apache/cassandra/pull/776]
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-16209]
> Log Warning Rather than Verbose Trace when Preview Repair Validation
> Conflicts with Incremental Repair
> ------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16209
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16209
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Compaction
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When a preview repair on repaired data identifies which SSTables to validate,
> it might come across an SSTable that's still pending for an in-progress
> incremental repair session. It makes sense that we immediately fail the
> preview repair in that case, but the resulting error and verbose stack trace
> in the logs is a bit too severe a reaction. We should downgrade this to a
> simple warning message.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
