You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Arvind Nithrakashyap (JIRA)" <ji...@apache.org> on 2016/10/12 07:39:20 UTC
[jira] [Updated] (CASSANDRA-12778) Tombstones not being deleted
when only_purge_repaired_tombstones is enabled
[ https://issues.apache.org/jira/browse/CASSANDRA-12778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Nithrakashyap updated CASSANDRA-12778:
---------------------------------------------
Summary: Tombstones not being deleted when only_purge_repaired_tombstones is enabled (was: Tombstones not being Deleted when only_purge_repaired_tombstones is enabled)
> 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
> 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 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.3.4#6332)