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 2017/03/24 00:52:41 UTC
[jira] [Commented] (CASSANDRA-13313) Compaction leftovers not
removed on upgrade 2.1/2.2 -> 3.0
[ https://issues.apache.org/jira/browse/CASSANDRA-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939503#comment-15939503 ]
Stefania commented on CASSANDRA-13313:
--------------------------------------
There was a similar discussion in CASSANDRA-12212 - albeit focused on using {{compactions_in_progress}} rather than ancestors. Other than counters created before 2.1, are you aware of any other possible consistency issues?
> Compaction leftovers not removed on upgrade 2.1/2.2 -> 3.0
> ----------------------------------------------------------
>
> Key: CASSANDRA-13313
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13313
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Reporter: Jeff Jirsa
> Assignee: Jeff Jirsa
> Priority: Minor
>
> Before 3.0 we used sstable ancestors to figure out if an sstable was left over after a compaction. In 3.0 the ancestors are ignored and instead we use LogTransaction files to figure it out. 3.0 should still clean up 2.1/2.2 compaction leftovers using the on-disk sstable ancestors when available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)