[ https://issues.apache.org/jira/browse/CASSANDRA-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939519#comment-15939519 ]
Jeff Jirsa commented on CASSANDRA-13313: ---------------------------------------- Oh I hadn't seen 12212 I have a patch where it's implemented with {{compactions_in_progress}} and re-added (but deprecated) ancestors to metadata , but hadn't finished the dtest. My expectation was the only consistency issue is counters but there are other resource issues (disk space, memory on reads if there are a lot of tombstones, etc). I'm not sure how vital it is - I marked it minor and it's low on my queue, but if consensus is it's truly a won't-fix I'm not sure I'll fight that. > 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)