Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 21 Jul 2011 13:21:59 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1657354012.11383.1311254519780.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1982482419.38230.1308941027423.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2825) Auto bootstrapping the 4th node
 in a 4 node cluster doesn't work, when no token explicitly assigned in
 config.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams commented on CASSANDRA-2825:
---------------------------------------------

Impressive, I have no idea how this is breaking testTokenRoundtrip():

{noformat}
    public void testTokenRoundtrip() throws Exception
    {  
        StorageService.instance.initServer();
        // fetch a bootstrap token from the local node
        assert BootStrapper.getBootstrapTokenFrom(FBUtilities.getLocalAddress()) != null;
    }
{noformat}

The log just shows a bunch of attempts to connect to the seed (127.0.0.2) which hasn't started yet.

> Auto bootstrapping the 4th node in a 4 node cluster doesn't work, when no token explicitly assigned in config.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2825
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2825
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.0, 0.8.1
>            Reporter: Michael Allen
>            Assignee: Brandon Williams
>             Fix For: 0.8.2
>
>         Attachments: 2825-v2.txt, 2825.txt
>
>
> This was done in sequence.  A, B, C, and D.  Node A with token 0 explicitly set in config.  The rest with auto_bootstrap: true and no token explicitly assigned.  B and C work as expected. D ends up stealing C's token.  
> from system.log on C:
> INFO [GossipStage:1] 2011-06-24 16:40:41,947 Gossiper.java (line 638) Node /10.171.47.226 is now part of the cluster
> INFO [GossipStage:1] 2011-06-24 16:40:41,947 Gossiper.java (line 606) InetAddress /10.171.47.226 is now UP
> INFO [GossipStage:1] 2011-06-24 16:42:09,432 StorageService.java (line 769) Nodes /10.171.47.226 and /10.171.55.77 have the same token 61078635599166706937511052402724559481.  /10.171.47.226 is the new owner
> WARN [GossipStage:1] 2011-06-24 16:42:09,432 TokenMetadata.java (line 120) Token 61078635599166706937511052402724559481 changing ownership from /10.171.55.77 to /10.171.47.226

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira