Hi Aaron, Rob,
Thanks for the information, I will try it.
Regards,
Boris
On Tue, May 22, 2012 at 11:47 PM, Rob Coli wrote:
> On Tue, May 22, 2012 at 3:00 AM, aaron morton
> wrote:
> > 1) Isolating the node from the cluster to stop write activity. You can
> > either start the node with the -Dc
On Tue, May 22, 2012 at 3:00 AM, aaron morton wrote:
> 1) Isolating the node from the cluster to stop write activity. You can
> either start the node with the -Dcassandra.join_ring=false JVM option or
> use nodetool disablethrift and disablegossip to stop writes. Note that this
> will not stop ex
CASSANDRA-3712 has not been applied to 0.8.X.
If I understand the problem correctly the issue is 0.8.10.
You may be able to avoid the race condition by:
1) Isolating the node from the cluster to stop write activity. You can either
start the node with the -Dcassandra.join_ring=false JVM opti
Hi,
We are currently running 0.8.10 with 4 nodes. We tried to re-balance the
range each node owns by using "nodetool move". After moving the node to the
assigned token, we run the cleanup command, then we saw the exceptions:
Error occured during cleanup
java.util.concurrent.ExecutionException:
