On Fri, May 2, 2014 at 12:29 AM, Jan Kesten wrote:
> I'm running a cassandra cluster with 2.0.6 and 6 nodes. As far as I know,
> routine repairs are still mandatory for handling tombstones - even I
> noticed that the cluster now does a "snapshot-repair" by default.
>
> Now my cluster is running a
Hi,
to be honest 2 days for 200GB nodes doesn't sound too unreasonable to me
(depending on your hardware of course). We were running a ~20 GB cluster
with regualr hard drives (no SSD) and our first repair ran a day as well
if I recall correctly. We since improved our hardware and got it down t
Hi Duncan,
is it actually doing something or does it look like it got stuck?
2.0.7 has a fix for a getting stuck problem.
it starts with sending merkle trees and streaming for some time (some
hours in fact) and then seems just to hang. So I'll try to update and
see it that's solves the issu
Hi Jan,
On 02/05/14 09:29, Jan Kesten wrote:
Hello together,
I'm running a cassandra cluster with 2.0.6 and 6 nodes. As far as I know,
routine repairs are still mandatory for handling tombstones - even I noticed
that the cluster now does a "snapshot-repair" by default.
Now my cluster is runnin
Hello together,
I'm running a cassandra cluster with 2.0.6 and 6 nodes. As far as I
know, routine repairs are still mandatory for handling tombstones - even
I noticed that the cluster now does a "snapshot-repair" by default.
Now my cluster is running a while and has a load of about 200g per n
