You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2018/12/14 13:52:00 UTC
[jira] [Updated] (CASSANDRA-14936) Anticompaction should throw
exceptions on errors, not just log them
[ https://issues.apache.org/jira/browse/CASSANDRA-14936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-14936:
----------------------------------------
Reviewer: Blake Eggleston
Status: Patch Available (was: Open)
patch: https://github.com/krummas/cassandra/commits/marcuse/14936
tests: https://circleci.com/workflow-run/bf69001c-756b-4c43-a754-652066dca07f
Note that this also makes anticompactions unstoppable again to make sure that starting a conflicting AC fails by timing out when trying to cancel compactions. CASSANDRA-14935 will improve this behaviour by failing immediately if any conflicting AC is active and make them stoppable again.
> Anticompaction should throw exceptions on errors, not just log them
> -------------------------------------------------------------------
>
> Key: CASSANDRA-14936
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14936
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Major
> Fix For: 4.0
>
>
> Anticompaction currently catches any exceptions and just logs them instead of rethrowing, this can cause us to overstream and leave sstables unrepaired.
> This was made more likely to happen with CASSANDRA-14397 (before that anticompactions could not be stopped at all).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org