cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt Greaves (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13142) Upgradesstables cancels compactions unnecessarily
Date Fri, 20 Jan 2017 16:48:26 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832084#comment-15832084
] 

Kurt Greaves commented on CASSANDRA-13142:
------------------------------------------

I've already done all the necessary reconnaissance so will write a patch soon, I think best
solution would be to provide a more modular way to specify compaction types to "ignore" in
{{CompactionManager.interruptCompactionsForCFs()}}. 

> Upgradesstables cancels compactions unnecessarily
> -------------------------------------------------
>
>                 Key: CASSANDRA-13142
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13142
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Kurt Greaves
>            Assignee: Kurt Greaves
>            Priority: Minor
>
> Since at least 1.2 upgradesstables will cancel any compactions bar validations when run.
This was originally determined as a non-issue in CASSANDRA-3430 however can be quite annoying
(especially with STCS) as a compaction will output the new version anyway. Furthermore, as
per CASSANDRA-12243 it also stops things like view builds and I assume secondary index builds
as well which is not ideal.
> We should avoid cancelling compactions unnecessarily.
> I'd class this as a very minor bug, should at least be fixed from 3.0, but up for debate.
The main negative effect is annoying operators (which I tend to rate pretty highly), but other
than that there are no serious consequences.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message