.
May be more experieced guys can comment on this to help u :)
Thanks
Anuj
Sent from Yahoo Mail on Android
From:"Badrjan"
Date:Sun, 15 Nov, 2015 at 6:14 pm
Subject:Re: Repair time comparison for Cassandra 2.1.11
Repairs are parallel. The only error-ish message I see in the log o
quot; <> badr...@tuta.io> >
> Date> :Sun, 15 Nov, 2015 at 5:39 pm
> Subject> :Re: Repair time comparison for Cassandra 2.1.11
>
> Nothing is being dropped plus the processor is busy around 60%.
> B.
>
> 15. Nov 2015 15:58 by > anujw_2...@yahoo.co.in>
while repair is running?
50 hours seems too much considering your cluster is stable and you dont have
any dropped mutations on any of the nodes.
Thanks
Anuj
Sent from Yahoo Mail on Android
From:"Badrjan"
Date:Sun, 15 Nov, 2015 at 5:39 pm
Subject:Re: Repair time comparison for
sure that there no mutation drops.
> Thanks> Anuj
>
>
> Sent from Yahoo Mail on Android
>
> > From> :"> badr...@tuta.io> " <> badr...@tuta.io> >
> Date> :Sun, 15 Nov, 2015 at 4:20 pm
> Subject> :Repair time comparison for Cassandra 2.1.1
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:"badr...@tuta.io"
Date:Sun, 15 Nov, 2015 at 4:20
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.
