You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Caleb Rackliffe (Jira)" <ji...@apache.org> on 2020/10/13 17:18:00 UTC
[jira] [Updated] (CASSANDRA-16209) Log Warning Rather than Verbose
Trace when Preview Repair Validation Conflicts with Incremental Repair
[ https://issues.apache.org/jira/browse/CASSANDRA-16209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Caleb Rackliffe updated CASSANDRA-16209:
----------------------------------------
Change Category: Operability
Complexity: Low Hanging Fruit
Fix Version/s: 4.0-beta
Assignee: Caleb Rackliffe
Status: Open (was: Triage Needed)
> 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
>
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org