We had originally started with 3 nodes w/ 32GB ram and 768GB SSDs. I pretty
much Google'd my way into setting up cassandra and set it up using tokens
because I was following an older docco. We were using Cassandra 1.2.5, I
learned about vnodes later on and regretted waking up that morning.
1.)
On Wed, Sep 18, 2013 at 4:26 PM, Nimi Wariboko Jr
wrote:
> 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).
>
Are you saying that (other than the imbalance that is the
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
-- AddressLoad Tokens Owns Ho
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 indica
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
