Thomas Whaples created CASSANDRA-4440:
-----------------------------------------
Summary: Better output desired to diagnose hung bootstrap due to
partial connectivity
Key: CASSANDRA-4440
URL: https://issues.apache.org/jira/browse/CASSANDRA-4440
Project: Cassandra
Issue Type: Improvement
Components: Core
Reporter: Thomas Whaples
Priority: Trivial
Fix For: 0.8.10
I was attempting to set up a new node and bootstrap it into my cluster.
Due to an error in my network configuration, this node was able to communicate
with only a portion of the existing nodes (it could connect to 3 out of 5
existing nodes). As a result, the node transferred some data, but ultimately
got stuck in a state of 'Joining' the cluster and not doing anything.
Unfortunately, it was a little tricky to diagnose. I only figured it out when I
turned on debug-level monitoring and saw a message about trying to establish an
outbound connection (not a *failure* to establish it, just a note that it was
trying to establish one. I'd quote it, but the debug logs got rotated in the
logspew.)
For posterity, I would like to request that a node in this sort of a situation
present additional messages or other diagnostics.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
