[
https://issues.apache.org/jira/browse/CASSANDRA-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173506#comment-13173506
]
Vijay commented on CASSANDRA-3631:
----------------------------------
Hibernate code is helpful only when we replace a node with the same IP. When a
node comes back with the same IP and token, other nodes in the cluster will
mark it UP because they know the token before it went down, hence we are
setting hibernate so they will still think the node is down. Meanwhile we will
stream the data and once the stream is completed we will mark that node as
normal which will trigger hints to be streamed in.
For nodes which are not replaced with the same IP this code is useless and
harmless as they are not in the tokenMetadata they will not be considered part
of the ring or will be considered as up until we set the token. Makes sense?
By removing the hibernate code we will not be able to do the above. As "nt
ring" is looking for the getTokenToEndpointMap() and then looks for the nodes
are up or down, Unless we change the way "nt ring" works to show nodes which
are gossiping (This might include fat clients till they are removed).
In a normal bootstrap case we still dont know the token, untill we have
selected the token. hope i am making sense.
> 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
