se finds it inadequate, speak up.
>>
>> -- Jack Krupansky
>>
>> -Original Message- From: Paolo Crosato
>> Sent: Thursday, June 19, 2014 10:13 AM
>> To: user@cassandra.apache.org
>> Subject: Best practices for repair
>>
>>
>> Hi e
assandra.apache.org>
Subject: Best practices for repair
Hi eveybody,
we have some problems running repairs on a timely schedule. We have a
three node deployment, and we start repair on one node every week,
repairing one columnfamily by one.
However, when we run into the big co
tation/cassandra/2.0/
> cassandra/operations/ops_repair_nodes_c.html
>
> If you or anybody else finds it inadequate, speak up.
>
> -- Jack Krupansky
>
> -Original Message- From: Paolo Crosato
> Sent: Thursday, June 19, 2014 10:13 AM
> To: user@cassandra.apache.org
&g
, 2014 10:13 AM
To: user@cassandra.apache.org
Subject: Best practices for repair
Hi eveybody,
we have some problems running repairs on a timely schedule. We have a
three node deployment, and we start repair on one node every week,
repairing one columnfamily by one.
However, when we run into the big
Hi eveybody,
we have some problems running repairs on a timely schedule. We have a
three node deployment, and we start repair on one node every week,
repairing one columnfamily by one.
However, when we run into the big column families, usually repair
sessions hangs undefinitely, and we have to
