I would zero in on network throughput, especially interrack trunks
sent from my mobile
Daemeon Reiydelle
skype daemeon.c.m.reiydelle
USA 415.501.0198
On Mar 17, 2017 2:07 PM, "Roland Otta" wrote:
> hello,
>
> we are quite inexperienced with cassandra at the moment and are playing
> around with
.
Enabling gc logging helps as well to see the impact.
From: Roland Otta
Date: Monday, March 20, 2017 at 1:53 AM
To: Conversant , "user@cassandra.apache.org"
Subject: Re: repair performance
good point! i did not (so far) i will do that - especially because i often see
all compacti
ummit-2016
From: Roland Otta
Date: Friday, March 17, 2017 at 5:47 PM
To: "user@cassandra.apache.org"
Subject: Re: repair performance
did not recognize that so far.
thank you for the hint. i will definitely give it a try
On Fri, 2017-03-17 at 22:32 +0100, benjamin roth wrote:
The fork f
dra-summit-2016
From: Roland Otta
Date: Friday, March 17, 2017 at 5:47 PM
To: "user@cassandra.apache.org"
Subject: Re: repair performance
did not recognize that so far.
thank you for the hint. i will definitely give it a try
On Fri, 2017-03-17 at 22:32 +0100, benjamin roth
did not recognize that so far.
thank you for the hint. i will definitely give it a try
On Fri, 2017-03-17 at 22:32 +0100, benjamin roth wrote:
The fork from thelastpickle is. I'd recommend to give it a try over pure
nodetool.
2017-03-17 22:30 GMT+01:00 Roland Otta
mailto:roland.o...@willhaben.
The fork from thelastpickle is. I'd recommend to give it a try over pure
nodetool.
2017-03-17 22:30 GMT+01:00 Roland Otta :
> forgot to mention the version we are using:
>
> we are using 3.0.7 - so i guess we should have incremental repairs by
> default.
> it also prints out incremental:true when
... maybe i should just try increasing the job threads with --job-threads
shame on me
On Fri, 2017-03-17 at 21:30 +, Roland Otta wrote:
forgot to mention the version we are using:
we are using 3.0.7 - so i guess we should have incremental repairs by default.
it also prints out incremental:tr
forgot to mention the version we are using:
we are using 3.0.7 - so i guess we should have incremental repairs by default.
it also prints out incremental:true when starting a repair
INFO [Thread-7281] 2017-03-17 09:40:32,059 RepairRunnable.java:125 - Starting
repair command #7, repairing keyspac
It depends a lot ...
- Repairs can be very slow, yes! (And unreliable, due to timeouts, outages,
whatever)
- You can use incremental repairs to speed things up for regular repairs
- You can use "reaper" to schedule repairs and run them sliced, automated,
failsafe
The time repairs actually may var
