I got myself into a situation where one node (10.47.108.100) has a lot more
data than the other nodes. In fact, the 1 TB disk on this node is almost
full. I added 3 new nodes and let cassandra automatically calculate new tokens
by taking the highest loaded nodes. Unfortunately there is
Because you were able to successfully run repair you can follow up with
a nodetool cleanup which will git rid of some of the extraneous data on
that (bigger) node. You're also assured after you run repair that
entropy beteen the nodes is minimal.
Assuming you're using the random ordered
Thanks Ben. That's what I was afraid I had to do. I can see how it's a lot
easier if you simply double the cluster when adding capacity.
Jon
On Jun 9, 2011, at 4:44 PM, Benjamin Coverston wrote:
Because you were able to successfully run repair you can follow up with a
nodetool cleanup
