[
https://issues.apache.org/jira/browse/CASSANDRA-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173142#comment-13173142
]
Brandon Williams commented on CASSANDRA-3631:
---------------------------------------------
bq. the problem with making the default to be joining is that it will mark the
server up
I had another thought. When replacing a token, don't we know that up front
with DD.getReplaceToken? So we can use that as a check as to whether we should
start up in hibernate or joining. (I still like the idea of hibernate showing
up as initializing though)
> While sleeping for RING_DELAY, bootstrapping nodes do not show as joining in
> the ring (or at all)
> -------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-3631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3631
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Brandon Williams
> Assignee: Vijay
> Priority: Minor
> Fix For: 1.0.7
>
>
> As the title says, the nodes do not show in the ring until they are actually
> in the token selection/streaming phase. This appears due to CASSANDRA-957,
> but now can be further exacerbated by longer sleep times for CASSANDRA-3629.
--
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
