cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: how to solve one node is in heavy load in unbalanced cluster
Date Sun, 31 Jul 2011 21:43:50 GMT
> aaron suggested it's better to run node repair on every node then re-balance it.

That's me been cautious with other peoples data.

It looks like node 3 is overwhelmed. Try getting the move sorted. 

Cheers

-----------------
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com

On 1 Aug 2011, at 05:48, Yan Chunlu wrote:

> is that okay to do nodetool move before a completely repair?
> 
> using this equation?
> def tokens(nodes):
> for x in xrange(nodes):
> print 2 ** 127 / nodes * x
> 
> On Mon, Aug 1, 2011 at 1:17 AM, mcasandra <mohitanchlia@gmail.com> wrote:
> First run nodetool move and then you can run nodetool repair. Before you run
> nodetool move you will need to determine tokens that each node will be
> responsible for. Then use that token to perform move.
> 
> --
> View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/how-to-solve-one-node-is-in-heavy-load-in-unbalanced-cluster-tp6630827p6638649.html
> Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.
> 


Mime
View raw message