Re: LCS, range tombstones, and eviction

That makes sense. I see however some unexpected performance data on my test, but I will start another thread for that. Thanks again! On Fri, May 12, 2017 at 6:56 PM, Blake Eggleston wrote: > The start and end points of a range tombstone are basically stored as > special

Re: LCS, range tombstones, and eviction

The start and end points of a range tombstone are basically stored as special purpose rows alongside the normal data in an sstable. As part of a read, they're reconciled with the data from the other sstables into a single partition, just like the other rows. The only difference is that they

Re: LCS, range tombstones, and eviction

Thanks a lot Blake, that definitely helps! I actually found a ticket re range tombstones and how they are accounted for: https://issues.apache.org/jira/browse/CASSANDRA-8527 I am wondering now what happens when a node receives a read request. Are the range tombstones read before scanning the

Re: LCS, range tombstones, and eviction

Hi Stefano, Based on what I understood reading the docs, if the ratio of garbage  collectable tomstones exceeds the "tombstone_threshold", C* should start  compacting and evicting. If there are no other normal compaction tasks to be run, LCS will attempt to compact the sstables it estimates it

LCS, range tombstones, and eviction

Hi all, I am trying to wrap my head around how C* evicts tombstones when using LCS. Based on what I understood reading the docs, if the ratio of garbage collectable tomstones exceeds the "tombstone_threshold", C* should start compacting and evicting. I am quite puzzled however by what might