[
https://issues.apache.org/jira/browse/CASSANDRA-16209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17218533#comment-17218533
]
David Capwell commented on CASSANDRA-16209:
-------------------------------------------
You mean
https://app.circleci.com/pipelines/github/dcapwell/cassandra/705/workflows/e53c72aa-dc4c-4dcc-811d-87aedd75f89a/jobs/3931
consistency_test.py::TestConsistency::test_12872?
I remember this test class failing but didn't check if there was a jira; took
the fact it passed in the other version to tell me it was flaky.
> 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-beta3
>
> 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]
