Jonathan, for all of us just tinker with test clusters, building confidence in the product, it would be nice to be able to do same with nodetool, without jconsole, just my 0.5 penny. Thanks.
Jonathan Ellis-3 wrote: > > From the next paragraph of the same wiki page: > > 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 Cassandra will force one itself if it detects that it > is low on space. A compaction marker is also added to obsolete > sstables so they can be deleted on startup if the server does not > perform a GC before being restarted. > > On Tue, Mar 22, 2011 at 8:30 AM, Jonathan Colby > <jonathan.co...@gmail.com> wrote: > > According to the Wiki Page on compaction: once compaction is > finished, the old SSTable files may be deleted* > > > > * http://wiki.apache.org/cassandra/MemtableSSTable > > > > I thought the old SSTables would be deleted automatically, but this > wiki page got me thinking otherwise. > > > > Question is, if it is true that old SSTables must be manually > deleted, how can one safely identify which SSTables can be deleted?? > > > > Jon > > > > > > > > > > > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com > -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Deleting-old-SSTables-tp6196113p6198172.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
