Thanks for the tip. Checked nodetool ring on all nodes and they all have a
consistent view of the ring. We have had other problems like nodes crashing
etc so anything could have happened, but we're sure we didnt issue a nodetool
move command.
From: Tyler Hobbs [mailto:ty...@datastax.com]
Nodes don't move themselves, you likely have some kind of 'bouncing
gossip' issue where a node was removed/replaced and is hanging around,
but only periodically held in statee between nodes. Unfortunately
node removal is very prone to this before 0.8.3 and even after that,
you can't fix it
We have a 10 node cluster (v0.7.9) split into 2 datacenters. Three times we
have seen nodes move themselves to different locations in the ring. In each
case, the move unbalanced the ring. In one case a node moved to the opposite
side of the ring.
Sometime after the first spontaneous move we
OpsCenter just periodically calls describe_ring() on different nodes in the
cluster, so that's how it's getting that information.
Maybe try running nodetool ring on each node in your cluster to make sure
they all have the same view of the ring?
On Fri, Jun 1, 2012 at 4:01 PM, Curt Allred
