[
https://issues.apache.org/jira/browse/CASSANDRA-12212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389600#comment-15389600
]
Jeremiah Jordan commented on CASSANDRA-12212:
---------------------------------------------
I have just been told that not using compactions in progress can result in bad
things happening to counters and possibly other places. If that is no longer
the case case in 2.1 great. But if that is no longer the case why do we still
track them there? My thought here was purely "if we hadn't upgraded to 3.0 we
would be consulting compactions in progress" so the first upgrade to 3.0 should
consult compactions in progress.
> 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)
