[
https://issues.apache.org/jira/browse/CASSANDRA-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601043#comment-13601043
]
Kristoffer Carlson commented on CASSANDRA-5129:
-----------------------------------------------
I'm still experiencing this on 1.2.2. Same exception and same result. I took a
thread dump and it didn't have anything interesting in it.
> newly bootstrapping nodes hang indefinitely in STATUS:BOOT while JOINING
> cluster
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-5129
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5129
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.0
> Environment: Ubuntu 12.04
> Reporter: Michael Kjellman
> Assignee: Brandon Williams
> Fix For: 1.2.2
>
>
> bootstrapping a new node causes it to hang indefinitely in STATUS:BOOT
> Nodes streaming to the new node report
> {code}
> Mode: NORMAL
> Nothing streaming to /10.8.30.16
> Not receiving any streams.
> Pool Name Active Pending Completed
> Commands n/a 0 1843990
> Responses n/a 2 661750
> {code}
> the node being streamed to stuck in the JOINING state reports:
> {code}
> Mode: JOINING
> Not sending any streams.
> Nothing streaming from /10.8.30.103
> Nothing streaming from /10.8.30.102
> Pool Name Active Pending Completed
> Commands n/a 0 10
> Responses n/a 0 613577
> {code}
> it appears that the nodes in the "nothing streaming" state never sends a
> "finished streaming" to the joining node.
> no exceptions are thrown during the streaming on either node while the node
> is in this state.
> {code:name="full gossip state of bootstrapping node"}
> /10.8.30.16
> NET_VERSION:6
> RELEASE_VERSION:1.2.0
> STATUS:BOOT,127605887595351923798765477786913079289
> RACK:RAC1
> RPC_ADDRESS:0.0.0.0
> DC:DC1
> SCHEMA:5cd8420d-ce3c-3625-8293-67558a24816b
> HOST_ID:e20817ce-7454-4dc4-a1c6-b1dec35c4491
> LOAD:1.11824041581E11
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
