Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 20 Dec 2011 21:53:30 +0000 (UTC)
From: "Brandon Williams (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <142146583.32669.1324418010711.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1540416644.12244.1323889170741.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3631) While sleeping for RING_DELAY,
 bootstrapping nodes do not show as joining in the ring (or at all)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173538#comment-13173538 ] 

Brandon Williams commented on CASSANDRA-3631:
---------------------------------------------

Ok, I think I understand now.  We can't show up during the initial RING_DELAY because we don't have a token, but I accidentally made this a little worse with CASSANDRA-3629 by putting the 'wait for schema' logic in the wrong place.  I could instead get a token first and *then* wait on the schema (right before the call to bootstrap(token)) so at least the node shows up during this phase.  Does that sound accurate?


> 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