[
https://issues.apache.org/jira/browse/CASSANDRA-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay updated CASSANDRA-3631:
-----------------------------
Attachment: 0001-add-initializing-status-in-nodetool-for-3631.patch
Hi Brandon, Let me know if the attached patch is sufficient... It looks like
the following.
Address DC Rack Status State Load Owns
Token
143633478586163499463326301508681906517
10.123.42.165 us-east 1a Down Init ? ?
?
10.42.134.229 us-east 1a Up Normal 1.74 GB 35.40%
33724529808132598296109669138912087817
10.93.19.6 us-east 1a Down Normal 1.78 GB 38.69%
99546828780538918038465713665698202555
10.93.74.164 us-east 1a Up Normal 120.37 MB 2.53%
103845090001698524309715695190561870103
10.123.59.26 us-east 1a Up Normal 1.15 GB 23.39%
143633478586163499463326301508681906517
> 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
>
> Attachments: 0001-add-initializing-status-in-nodetool-for-3631.patch
>
>
> 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
