[ https://issues.apache.org/jira/browse/CASSANDRA-12778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson resolved CASSANDRA-12778. ----------------------------------------- Resolution: Not A Problem Please reopen if CASSANDRA-9143 does not solve this > Tombstones not being deleted when only_purge_repaired_tombstones is enabled > --------------------------------------------------------------------------- > > Key: CASSANDRA-12778 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12778 > Project: Cassandra > Issue Type: Bug > Reporter: Arvind Nithrakashyap > Assignee: Marcus Eriksson > Priority: Critical > > When we use only_purge_repaired_tombstones for compaction, we noticed that > tombstones are no longer being deleted. > {noformat}compaction = {'class': > 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy', > 'only_purge_repaired_tombstones': 'true'}{noformat} > The root cause for this seems to be caused by the fact that repair itself > issues a flush which in turn leads to a new sstable being created (which is > not in the repair set). It looks like we do have some old data in this > sstable because of this, only tombstones older than that timestamp are > getting deleted even though many more keys have been repaired. > Fundamentally it looks like flush and repair can race with each other and > with leveled compaction, the flush creates a new sstable at level 0 and > removes the older sstable (the one that is picked for repair). Since repair > itself seems to issue multiple flushes, the level 0 sstable never gets > repaired and hence tombstones never get deleted. > We have already included the fix for CASSANDRA-12703 while testing. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org