I noticed (and reported) a bug that made me drop this tool -->
https://github.com/BrianGallew/cassandra_range_repair/issues/16
Might this be related somehow ?
C*heers
Alain
2014-11-21 13:30 GMT+01:00 Paulo Ricardo Motta Gomes <
paulo.mo...@chaordicsystems.com>:
> Hey guys,
>
> Just reviving th
Hey guys,
Just reviving this thread. In case anyone is using the
cassandra_range_repair tool (https://github.com/BrianGallew/cassandra_range_
repair), please sync your repositories because the tool was not working
before due to a critical bug on the token range definition method. For more
informat
When I use virtual nodes, I typically use a much smaller number - usually in
the range of 10. This gives me the ability to add nodes easier without the
performance hit.
--
Colin Clark
+1-320-221-9531
> On Oct 28, 2014, at 10:46 AM, Alain RODRIGUEZ wrote:
>
> I have been trying this yest
I have been trying this yesterday too.
https://github.com/BrianGallew/cassandra_range_repair
"Not 100% bullet proof" --> Indeed I found that operations are done
multiple times, so it is not very optimised. Though it is open sourced so I
guess you can improve things as much as you want and contrib
https://github.com/BrianGallew/cassandra_range_repair
This breaks down the repair operation into very small portions of the ring
as a way to try and work around the current fragile nature of repair.
Leveraging range repair should go some way towards automating repair (this
is how the automatic re
On Mon, Oct 27, 2014 at 1:44 PM, Robert Coli wrote:
> On Mon, Oct 27, 2014 at 1:33 PM, Tim Heckman wrote:
>
>> I know that when issuing some operations via nodetool, the command blocks
>> until the operation is finished. However, is there a way to reliably
>> determine whether or not the operati
On Mon, Oct 27, 2014 at 1:33 PM, Tim Heckman wrote:
> I know that when issuing some operations via nodetool, the command blocks
> until the operation is finished. However, is there a way to reliably
> determine whether or not the operation has finished without monitoring that
> invocation of node
