cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Badrjan <badr...@tuta.io>
Subject Re: Repair time comparison for Cassandra 2.1.11
Date Sun, 15 Nov 2015 12:09:09 GMT
Nothing is being dropped plus the processor is busy around 60%. 
B.

15. Nov 2015 15:58 by anujw_2003@yahoo.co.in:


> Repair can take long time if you have lota of inconaistent data. If you 
> havent restarted nodes yet, you can  run nodetool tpstats command on all 
> nodes to make sure that there no mutation drops.
> Thanks> Anuj
>
>
> Sent from Yahoo Mail on Android
>
>  > From> :"> badrjan@tuta.io> " <> badrjan@tuta.io> >
> Date> :Sun, 15 Nov, 2015 at 4:20 pm
> Subject> :Repair time comparison for Cassandra 2.1.11
>
>  Hi,
> I have cluster of 4 machines With Cassandra 2.1.11,  SSD drives, 600 gb 
> data on each node (replication factor 3). 
> When I run partial repair on one node, it takes 50 hours to finish. Is that 
> normal? 
> B. >   
Mime
View raw message