This isn't the case. I noticed the error because of some unusual hotspotting. `nodetool status` also shows the cluster is unbalanced.
root@cass1:~# nodetool status Datacenter: 129 =============== Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns Host ID Rack UN 10.129.196.6 140.06 GB 269 21.8% ce8d4ea9-8106-44b3-a2dd-c0230eb53c94 196 UN 10.129.196.21 157.84 GB 256 22.4% d7009278-3191-48a1-8112-dc350e78b783 196 UN 10.129.196.4 138.52 GB 260 23.4% cde6c3be-a066-47f2-abc2-b1d78bee0d7c 196 UN 10.129.196.5 261.46 GB 239 32.3% 2cb24510-2f89-46b2-96b9-873f8e8e50da 196 On Wednesday, September 18, 2013 at 4:53 PM, Nick Bailey wrote: > OpsCenter only supports vnodes minimally at this point. > > More specifically, it chooses a random token that a node owns in order to > display that node on the ring. So a vnode cluster will always appear > unbalanced in OpsCenter. Your cluster is probably balanced fine, but 'nodetoo > status' should indicate that. > > Better vnode support is coming up in a future OpsCenter release. > > > On Wed, Sep 18, 2013 at 6:26 PM, Nimi Wariboko Jr <nimiwaribo...@gmail.com > (mailto:nimiwaribo...@gmail.com)> wrote: > > Hi, > > > > When I started with cassandra I had originally set it up to use tokens. I > > then migrated to vnodes (using shuffle), but my cluster isn't balanced > > (http://imgur.com/73eNhJ3). > > > > What steps can I take to balance my cluster? > > > > Thanks, > > Nimi > > > > >
