I'll add that while we don't see either of the nodes with the range
that failed marked as down one of them *does* appear to have a late
arrival of the cluster of UP messages that happens just after the
bootstrap fails:
$ egrep 'JOIN|Illegal|10.11.12.14|10.11.12.13' system.log | grep -v ^DEBUG
IN
Neither of the two nodes identified as having the range that
IllegalStateException reports are mentioned by FailureDetector.java.
There are 5 endpoints that FailureDetector says are 'unknown endpoint'
but all of them are reported as "UP" by Gossiper.java before the
"schema complete, ready to boots
Hi Peter,
At the time of the IllegalStateException, do you see the node that it
should be streaming from marked as down by the failure detector?
Mark
On Fri, Aug 15, 2014 at 5:45 AM, Peter Haggerty
wrote:
> When adding nodes via bootstrap to a 27 node 2.0.9 cluster with a
> cluster-wide phi_
