You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Stefania (JIRA)" <ji...@apache.org> on 2016/08/01 07:49:20 UTC

[jira] [Commented] (CASSANDRA-12212) system.compactions_in_progress needs to be used on first upgrade to 3.0

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

Stefania commented on CASSANDRA-12212:
--------------------------------------

Thanks for clarifying. If I understood correctly, given that when local shards get reconciled with global shards we take the global shard, and counter mutations in 2.1+ create global shards, we shouldn't have any compactions in progress that need to reconcile two local shards unless people have been using 2.1 only for a very short period of time. So the only legitimate case would be the case when 2.1 is installed as an intermediate release before upgrading to 3.0. Is this accurate?

> system.compactions_in_progress needs to be used on first upgrade to 3.0
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-12212
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12212
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction
>            Reporter: Jeremiah Jordan
>            Assignee: Stefania
>             Fix For: 3.0.x, 3.x
>
>
> CASSANDRA-7066 removed the system.compactions_in_progress table and replaced it with the new transaction system.  But system.compactions_in_progress needs to be consulted for the first startup after upgrading from 2.1 to 3.0.



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