@cassandra.apache.org
*Subject:* RE: Tombstone gc after gc grace seconds
Hi,
I saw there are 2 more interesting parameters -
a. tombstone_threshold - A ratio of garbage-collectable tombstones
to all contained columns, which if exceeded by the SSTable triggers
compaction (with no other
and columns are added throughout the day. 300K columns on
an average per rowKey.
From: Alain RODRIGUEZ [mailto:arodr...@gmail.com]
Sent: Friday, January 30, 2015 4:26 AM
To: user@cassandra.apache.org
Subject: Re: Tombstone gc after gc grace seconds
The point is that all the parts or fragments
[mailto:migh...@gmail.com migh...@gmail.com]
*Sent:* Monday, January 26, 2015 12:11 PM
*To:* user@cassandra.apache.org
*Subject:* Re: Tombstone gc after gc grace seconds
My understanding is consistent with Alain's, there's no way to force a
tombstone-only compaction, your only option is major
: Monday, January 26, 2015 12:11 PM
To: user@cassandra.apache.org
Subject: Re: Tombstone gc after gc grace seconds
My understanding is consistent with Alain's, there's no way to force a
tombstone-only compaction, your only option is major compaction. If you're
using size tiered, that comes
To: user@cassandra.apache.org
Subject: RE: Tombstone gc after gc grace seconds
Hi,
I saw there are 2 more interesting parameters –
a. tombstone_threshold - A ratio of garbage-collectable tombstones to all
contained columns, which if exceeded by the SSTable triggers compaction (with
no other
My understanding is consistent with Alain's, there's no way to force a
tombstone-only compaction, your only option is major compaction. If you're
using size tiered, that comes with its own drawbacks.
I wonder if there's a technical limitation that prevents introducing a
shadowed data cleanup
I don't think that such a thing exists as SSTables are immutable. You
compact it entirely or you don't. Minor compaction will eventually evict
tombstones. If it is too slow, AFAIK, the better solution is a major
compaction.
C*heers,
Alain
2015-01-23 0:00 GMT+01:00 Ravi Agrawal
