Re: Unbalanced ring after upgrade!

Actually, doing a nodetool ring is always showing the current node as owning 99% of the ring From db-1a-1: Address DC RackStatus State Load Effective-Ownership Token Token(bytes[eaa8]) 10.0.4.22 us-east 1a Up

Unbalanced ring after upgrade!

Hello, We just upgraded from 1.1.2->1.1.9. We utilize the byte ordered partitioner (we generate our own hashes). We have not yet upgraded sstables. Before the upgrade, we had a balanced ring. After the upgrade, we see: 10.0.4.22 us-east 1a Up Normal 77.66 GB