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 2019/05/10 12:16:00 UTC
[jira] [Updated] (CASSANDRA-15123) Avoid keeping sstables marked
forever when user defined compaction gets interrupted
[ https://issues.apache.org/jira/browse/CASSANDRA-15123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-15123:
----------------------------------------
Severity: Normal
Complexity: Low Hanging Fruit
Discovered By: User Report
Bug Category: Parent values: Degradation(12984)Level 1 values: Resource Management(12995)
Status: Open (was: Triage Needed)
> Avoid keeping sstables marked forever when user defined compaction gets interrupted
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-15123
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15123
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
>
> When we have both repaired + unrepaired data on a node, we create multiple compaction tasks and run them serially. If one of those tasks gets interrupted or throws exception we will keep sstables in the other tasks as compacting forever.
--
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