cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Ng <berryt...@gmail.com>
Subject Re: Repair Process Taking too long
Date Tue, 10 Apr 2012 17:33:36 GMT
I have 12 nodes with approximately 1TB load per node.  The RF is 3.  I am
considering moving to ext4.

I checked the ranges and the numbers go from 1 to the 9000s .

On Tue, Apr 10, 2012 at 12:56 PM, Jonathan Rhone <rhone@tinyco.com> wrote:

> Data size, number of nodes, RF?
>
> Are you using size-tiered compaction on any of the column families that
> hold a lot of your data?
>
> Do your cassandra logs say you are streaming a lot of ranges?
> zgrep -E "(Performing streaming repair|out of sync)"
>
>
> On Tue, Apr 10, 2012 at 9:45 AM, Igor <igor@4friends.od.ua> wrote:
>
>>  On 04/10/2012 07:16 PM, Frank Ng wrote:
>>
>> Short answer - yes.
>> But you are asking wrong question.
>>
>>
>> I think both processes are taking a while.  When it starts up, netstats
>> and compactionstats show nothing.  Anyone out there successfully using ext3
>> and their repair processes are faster than this?
>>
>>  On Tue, Apr 10, 2012 at 10:42 AM, Igor <igor@4friends.od.ua> wrote:
>>
>>> Hi
>>>
>>> You can check with nodetool  which part of repair process is slow -
>>> network streams or verify compactions. use nodetool netstats or
>>> compactionstats.
>>>
>>>
>>> On 04/10/2012 05:16 PM, Frank Ng wrote:
>>>
>>>> Hello,
>>>>
>>>> I am on Cassandra 1.0.7.  My repair processes are taking over 30 hours
>>>> to complete.  Is it normal for the repair process to take this long?  I
>>>> wonder if it's because I am using the ext3 file system.
>>>>
>>>> thanks
>>>>
>>>
>>>
>>
>>
>
>
> --
> Jonathan Rhone
> Software Engineer
>
> *TinyCo*
> 800 Market St., Fl 6
> San Francisco, CA 94102
> www.tinyco.com
>
>

Mime
View raw message