cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reverend Chip <>
Subject Re: repair takes two days, and ends up stuck: stream at 1096% (yes, really)
Date Mon, 15 Nov 2010 23:05:18 GMT
On 11/15/2010 2:01 PM, Jonathan Ellis wrote:
> On Mon, Nov 15, 2010 at 3:05 PM, Reverend Chip <> wrote:
>> There are a lot of non-tmps that were not included in the load
>> figure.  Having stopped the server and deleted tmp files, the data are
>> still using way more space than "ring" claimed -- and too much for
>> "cleanup" to work, as well:
>> Filesystem            Size  Used Avail Use% Mounted on
>> /dev/mapper/flashcache
>>                      932G  723G  162G  82% /var/lib/cassandra/data
> I take it you restarted it?  Does it show the correct load now?

I didn't expect that to be helpful.  But I'll try it.

>> Given that the previous situation included incomplete replication, I
>> can't just kill the node and let it repopulate.  So I can either magick
>> up more disk space or reload the whole cluster.  :-(
> You can move the data files do a node with more space, compact there,
> and move them back, but if you don't care about the data rebuilding is
> more straightforward.

The nodes are configured identically.  What's the point in just
compacting, anyway?  Do these files contain duplicate data, then?

View raw message