Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 18 Jul 2013 18:36:50 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12658249.1374065482215.74987.1374172610453@arcas>
In-Reply-To: <JIRA.12658249.1374065482215@arcas>
References: <JIRA.12658249.1374065482215@arcas>
Subject: [jira] [Commented] (CASSANDRA-5768) If a Seed can't be contacted, a
 new node comes up as a cluster of 1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams commented on CASSANDRA-5768:
---------------------------------------------

Your seed is 127.0.0.1, but your listen_address is something else.  So the behavior is actually correct, since it can't contact 127.0.0.1 since you're not listening there.
                
> If a Seed can't be contacted, a new node comes up as a cluster of 1
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-5768
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5768
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 2.0 beta 1
>            Reporter: Andy Cobley
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 2.0 beta 2
>
>         Attachments: 5768.txt, cassandra.yaml
>
>
> Setting up a new test cluster using  2.0.0-beta1 and I noticed the following behaviour with vnodes turned on.  
> I bring up one node all well and good.  however if I bring up a second node, that can't contact the first (the first being the seed for the second) after a short period of time, the second goes ahead and assumes it's the only node and bootstraps with all tokens.  
> NOTE also this email from Robert Coli 
> To: user@cassandra.apache.org
> Obviously if you have defined a seed and cannot contact it, the node should not start as a cluster of one. I have a to-do list item to file a JIRA on the subject, but if you wanted to file and link us, that'd be super. :)
> Startup trace (from the can't contact the seed messages below).
> http://aep.appspot.com/display/ABcWltCES1srzPrj5CkS69-GB8o/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira