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

Andy Cobley commented on CASSANDRA-5768:
----------------------------------------

I tried 5768.txt on cassandra-trunk.  It does halt cassandra if the seed can't 
be connected (with  java.lang.IllegalStateException: Unable to contact any 
seeds!)

However it also halts with the same exception if seeds is set to 127.0.0.1 (the 
default in cassandra.yaml):

seed_provider:
    # Addresses of hosts that are deemed contact points.
    # Cassandra nodes use this list of hosts to find each other and learn
    # the topology of the ring.  You must change this if you are running
    # multiple nodes!
    - class_name: org.apache.cassandra.locator.SimpleSeedProvider
      parameters:
          # seeds is actually a comma-delimited list of addresses.
          # Ex: "<ip1>,<ip2>,<ip3>"
          - seeds: "127.0.0.1"

So thats not correct I guess.
                
> 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
>
>
> 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: [email protected]
> 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

Reply via email to