You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2015/10/14 16:41:05 UTC
[jira] [Resolved] (CASSANDRA-10505) Duplicate range tombstones
[ https://issues.apache.org/jira/browse/CASSANDRA-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams resolved CASSANDRA-10505.
------------------------------------------
Resolution: Duplicate
Yeah, I think it was the fact that they were in a single sstable that threw me off, since the memtable should absorb those, but if it all comes down to a compaction problem it makes sense. Resolving as duplicate for 7953.
> Duplicate range tombstones
> --------------------------
>
> Key: CASSANDRA-10505
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10505
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Brandon Williams
> Fix For: 2.1.x
>
>
> I don't have a way to reproduce this just yet, but I have the sstables to prove it and can provide those offline. What I can reproduce, however, is the magnification of this problem via compaction. Here's what I know so far:
> * under some condition, we flush the exact same RT more than once in the same sstable. Same timestamps, everything.
> * Once this happens in multiple sstables, compacting them causes the duplication to grow. The more this occurs, the worse the problem gets.
> This continues until gc_grace has passed, then they are all evicted normally. I'd at least like to take a look at the compaction amplification for now, that way if the condition does occur, at least compaction can help it, rather than exacerbate it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)