On Tue, Apr 21, 2015 at 10:14 PM, Tiwari, Tarun tarun.tiw...@kronos.com
wrote:
I read that there was nodetool balance kind of command in Cassandra 0.7
but not anymore.
It never worked, really.
UN Node3 23.72 MB 1 0.4%
41a71df-7e6c-40ab-902f-237697eaaf3e rack1
UN Node2
Bring down the second node using nodetool removenode or decommission
Add the node with num_tokens and run the nodetool repair.
At last run the nodetool cleanup on both the nodes (one after the other)
Observe after some time using nodetool status.
On Apr 23, 2015 12:39 AM, Robert Coli
Hi,
While setting up a cluster for our POC, when we installed Cassandra on the 1st
node we gave num_tokens: 256 , while on next 2 nodes which were added later we
left it blank in Cassandra.yaml.
This made our cluster an unbalanced one with nodetool status showing 99% load
on one server. Now
