[
https://issues.apache.org/jira/browse/CASSANDRA-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Jirsa resolved CASSANDRA-13313.
------------------------------------
Resolution: Won't Fix
Wont-fixing this. Patch isn't hard, but dtest is annoying, and it's awfully
late in the 3.0 game to be worrying about this. Hate to add complexity to
3.0.15, just to yank it out in 4.0. Simple workaround is simple - stop
compactions, flush and drain during the upgrade, and chances of leftovers is
pretty low.
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
