cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Recovery from botched compaction
Date Thu, 15 Apr 2010 17:24:44 GMT
On Tue, Apr 13, 2010 at 3:59 PM, Anthony Molinaro
<anthonym@alumni.caltech.edu> wrote:
> I actually got lucky and while it hovered in the 91-95% full, compaction
> finished and its now at 60%.  However, I still have around a dozen or so
> data files.  I thought 'nodeprobe compact' did a major compaction, and
> that a major compaction would shrink to one file?

2 possibilities, probably both of which are affecting you:

1. If there isn't enough disk space to compact everything, cassandra
will remove files from the to-compact list until it has room to do
what you asked it to do.  (But, you you can still run out of space if
you write enough data while the compaction happens.)

2. 0.5's minor compactions don't combine as many sstables as they
should automatically.  This is fixed in 0.6

> Okay, sounds good, I may leave it for the moment, as last time I tried
> any sort of move/decommision with 0.5.x I was unable to figure out if
> anything was happening, so I may just wait and revisit when I upgrade.

Yes, 0.5 sucks there.  0.6 is still a little opaque but you can at
least see what is happening if you know where to look:
http://wiki.apache.org/cassandra/Streaming

-Jonathan

Mime
View raw message