Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of rev.chip@gmail.com designates
 74.125.83.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=VMs0xZ2tF3T6lZhuYePJtNiZ53mSQgNbW+dDHudEYe96mqFHOfcjlRx1WKr00rIJca
         p9OoG5BrnMKIYczVTi62TGMn7R/1lSaXH3330qELFpzqsof3Zgd/z1xOoTVdRUWUMz/Q
         ohtEDEUFcmya9jN3S7f7bI74SF0sasBjnc1Lc=
Message-ID: <4CE1BCAE.7090409@gmail.com>
Date: Mon, 15 Nov 2010 15:05:18 -0800
From: Reverend Chip <rev.chip@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: repair takes two days, and ends up stuck: stream at 1096% (yes,
 really)
References: <AANLkTikGKjEuFhMEJzcYjOocjZfL6AOThEkmQTkWiv0h@mail.gmail.com>
	<AANLkTikKLTVuB7QYLzW29w2C-YZvPxE=i26gmew9aEEx@mail.gmail.com>
	<AANLkTiniYJj80-2AOmfhzq3sQaPJ611RVqZCsUNwVo+N@mail.gmail.com>
	<AANLkTi=ecgbou9hwHERnWNep0of+G_kJbcdBG=tOxdja@mail.gmail.com>
	<4CE18415.9030303@gmail.com>
	<AANLkTinvAhVbV_4dA74EKJo-p1jKmwbquDX3BaAd62M-@mail.gmail.com>
	<4CE1A091.8070400@gmail.com>
 <AANLkTinKQTyR8twhAU3-kuoyJNq_Fs5GtSxnN30sZ9fh@mail.gmail.com>
In-Reply-To: <AANLkTinKQTyR8twhAU3-kuoyJNq_Fs5GtSxnN30sZ9fh@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 11/15/2010 2:01 PM, Jonathan Ellis wrote:
> On Mon, Nov 15, 2010 at 3:05 PM, Reverend Chip <rev.chip@gmail.com> 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?