cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13142) Upgradesstables cancels compactions unnecessarily
Date Thu, 20 Jul 2017 05:01:07 GMT

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

Jeff Jirsa commented on CASSANDRA-13142:
----------------------------------------

{quote} tests will need some serious thought{quote}

Byteman is your friend here - you can create a byteman rule pause the compaction after starting
it, and then test how upgradesstables interacts with that (running but not proceeding) compaction
task.


> 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
>         Attachments: 13142-v1.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message