Were you bootstrapping or otherwise moving nodes around?
I don't think anyone's tracked this bug down farther than "if you
restart the entire cluster, it goes away."
On Wed, May 19, 2010 at 10:05 PM, Keith Thornhill wrote:
> in a 5 node cluster, i noticed in our client error log that one of the
in a 5 node cluster, i noticed in our client error log that one of the
nodes was consistently throwing cassandra_UnavailableException during
a read operation.
looking into jmx, it was obvious that one of the node's view of the
ring was out of sync.
$ nodetool -host 192.168.20.150 ring
Address
