cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: disk full error while bootstrapping
Date Thu, 09 Sep 2010 14:25:20 GMT
On Thu, Sep 9, 2010 at 12:50 AM, Gurpreet Singh
<gurpreet.singh@gmail.com> wrote:
> 1. what is the purpose of this anticompacted file created during cleanup?

That is all the data that still belongs to the node, post-bootstrap.
Since you were just bringing the cluster back up to RF nodes, that's
all the data it started with still.  The older files will be removed
after the next JVM GC (or server restart, whichever comes first):
http://wiki.apache.org/cassandra/MemtableSSTable

> 2. compaction is also supposed to create a big file after reconciling the
> sstable files.. i see that anti-compaction is also creating a big file. How
> are these files going to be different?

Anticompaction is for splitting out one range of data from the rest.

> 3. Other than during streaming (bootstrapping), when is anti-compaction
> triggered?

It's not.

> 4. Now i have 240 gigs of disk used for probably around 92 gigs of useful
> data. When will the other files get deleted? Do i need to run compaction
> separately to take care of this.

Answered above.

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com

Mime
View raw message