> 1.2 w/ vnodes using LeveledCompactionStrategy, using 128 mb SSTables.
If you are using LCS the amount of overwritten / deleted data left will be
small.
Your row will be present in only 1 sstable per level. The number of levels is
included in the output from nodetool cfstats on the sstable cou
Thanks Rob.
Will checkout the tool you linked to. In our case it's definitely not the
tombstones hanging around since we write entire rows at once and the amount
of data in a row is far, far greater than the space a tombstone takes.
Jasdeep
On Fri, Oct 25, 2013 at 1:14 PM, Robert Coli wrote:
On Fri, Oct 25, 2013 at 1:10 PM, Jasdeep Hundal wrote:
>
> After performing a large set of deletes on our cluster, a few hundred
> gigabytes work (essentially cleaning out nearly all old data), we noticed
> that nodetool reported about the same load as before.
>
Tombstones are purgeable only aft
Does anyone have a good explanation or pointers to docs for understanding
how Cassandra decides to remove SSTables from disk?
After performing a large set of deletes on our cluster, a few hundred
gigabytes work (essentially cleaning out nearly all old data), we noticed
that nodetool reported about
