cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Huy Le <hu...@springpartners.com>
Subject Re: nodetool repair caused high disk space usage
Date Fri, 19 Aug 2011 18:34:04 GMT
I wasn't clear on that.  What I mean was would scrub putting data in at
state that might have caused the repair consume a lot of disk space?

On Thu, Aug 18, 2011 at 6:44 PM, aaron morton <aaron@thelastpickle.com>wrote:

> No scrub is a local operation only.
>
> Cheers
>
> -----------------
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 19/08/2011, at 6:36 AM, Huy Le wrote:
>
> Thanks.  I won't try that then.
>
> So in our environment, after upgrading from 0.6.11 to 0.8.4, we have to run
> scrub on all nodes before we can run repair on them.  Is there any chance
> that running scrub on the nodes causing data from all SSTables being
> streamed to/from other nodes on running repair?
>
> Huy
>
> On Thu, Aug 18, 2011 at 10:22 AM, Philippe <watcherfr@gmail.com> wrote:
>
>> Unfortunately repairing one cf at a time didn't help in my case because it
>> still streams all CF and that triggers lots of compactions
>> On Aug 18, 2011 3:48 PM, "Huy Le" <huyle@springpartners.com> wrote:
>>
>
>
>
> --
> Huy Le
> Spring Partners, Inc.
> http://springpadit.com
>
>
>


-- 
Huy Le
Spring Partners, Inc.
http://springpadit.com

Mime
View raw message