thx, that did the trick.
Jonathan Ellis wrote:
Added to http://wiki.apache.org/cassandra/MemtableSSTable:
SSTables that are obsoleted by a compaction are deleted asynchronously
when the JVM performs a GC. You can force a GC from jconsole if
necessary but this is not necessary; Cassandra will f
i have done no deletes, just inserts. so you are correct, there isn't
any "data" to cleanup. however when i run some of the cleanup and/or
compaction tasks the space used on disk actually grows, and i would like
to force any unneeded files to be removed. as i write this, jonathan
has respond
Added to http://wiki.apache.org/cassandra/MemtableSSTable:
SSTables that are obsoleted by a compaction are deleted asynchronously
when the JVM performs a GC. You can force a GC from jconsole if
necessary but this is not necessary; Cassandra will force one itself
if it detects that it is low on sp
Are you deleting data through the API or just doing a bunch of inserts
and then running a compaction? The latter will not result in anything
to clean up since data must be explicitly deleted.
b
On Tue, Apr 20, 2010 at 10:33 AM, B. Todd Burruss wrote:
> i'm trying to draw some correlation betwe
i'm trying to draw some correlation between the size of my data and the
space used on disk. i have set 1 so
there isn't any reason to keep data around.
my approach is this:
after only doing "puts" to cassandra for a while i stop my client and
want to perform the proper "cleanup" and/or "comp
