cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor <i...@4friends.od.ua>
Subject Re: Repair Process Taking too long
Date Tue, 10 Apr 2012 17:05:09 GMT
also - JVM heap size, and anything related to memory pressure

On 04/10/2012 07:56 PM, Jonathan Rhone 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 
> <mailto: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
>>     <mailto: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 <http://www.tinyco.com/>
>


Mime
View raw message