cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: Nodetool repair takes 4+ hours for about 10G data
Date Thu, 18 Aug 2011 22:52:48 GMT
The compactions ettings do not affect repair. (Thinking out loud, or does it ? Validation compactions
and table builds.)

Watch the logs or check 

nodetool compactionstats to see when the Validation completes completes.
and
nodetool netstats to see how long the data transfer takes

It sounds a little long. It could be either the time taken to work out the differences or
the time taken to stream the data across.

Cheers
 
-----------------
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com

On 19/08/2011, at 7:33 AM, Hefeng Yuan wrote:

> Hi,
> 
> Is it normal that the repair takes 4+ hours for every node, with only about 10G data?
If this is not expected, do we have any hint what could be causing this?
> 
> The ring looks like below, we're using 0.8.1. Our repair is scheduled to run once per
week for all nodes.
> 
> Compaction related configuration is like this:
> #concurrent_compactors: 1
> compaction_throughput_mb_per_sec: 16
> 
> Address         DC                 Rack   Load      Owns      
> 
> 10.150.13.92    Cassandra   RAC1  13.31 GB  16.67%    
> 10.150.12.61    Brisk             RAC1  5.89 GB   8.33%     
> 10.150.13.48    Cassandra   RAC1  8.62 GB   8.33%     
> 10.150.13.62    Cassandra   RAC1  12.62 GB  16.67%    
> 10.150.12.58    Brisk            RAC1  5.98 GB   8.33%     
> 10.150.13.88    Cassandra   RAC1  16.69 GB  8.33%     
> 10.150.13.89    Cassandra   RAC1  15.26 GB  16.67%    
> 10.150.12.62    Brisk            RAC1  3.72 GB   8.33%     
> 10.150.13.90    Cassandra   RAC1  35.01 GB  8.33% 
> 
> Thanks,
> Hefeng


Mime
View raw message