Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 30 May 2014 22:36:03 +0000 (UTC)
From: "Jason Brown (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12686197.1387828125588.50949.1401489363529@arcas>
In-Reply-To: <JIRA.12686197.1387828125588@arcas>
References: <JIRA.12686197.1387828125588@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-6523) "Unable to contact any
 seeds!" with multi-DC cluster and listen != broadcast address
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jason Brown edited comment on CASSANDRA-6523 at 5/30/14 10:34 PM:
------------------------------------------------------------------

[~cburroughs] Not sure how usable this suggestion is, but you could use the external addresses in the seeds list instead of the internal (or mixed per-dc). As GPFS is a 'reconnecting snitch', once the connection of the IP addr is established, the nodes in the same DC will switch over to the internal IP (listen_address). The length of time from node startup to switching the connection to internal IP should be rather short, so your traffic shouldn't be 'unusual' for much time. However, what happens during that 'unusual' time may be a deal breaker.

I bring this up as that's what we did when running multi-region in ec2, and is what EC2MRS facilitates. 


was (Author: jasobrown):
[~cburroughs] Not sure how usable this suggestion is, but you could use the external addresses in the seeds list instead of the internal (or mixed per-dc). As GPFS is a 'reconnecting snitch', once the connection of the IP addr is established, the nodes in the same DC will switch over to the internal IP (listen_address). The length of time from node startup to switching the connection to internal IP should be rather short, so your traffic shouldn't be 'unusual' for much time. However, what happens during that time may be a deal breaker for using the external IPs everywhere in the seeds list.

I bring this up as that's what we did when running multi-region in ec2, and is what EC2MRS facilitates. 

> "Unable to contact any seeds!" with multi-DC cluster and listen != broadcast address
> ------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6523
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6523
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: 1.2.13ish
>            Reporter: Chris Burroughs
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 1.2.17, 2.0.9, 2.1 rc1
>
>         Attachments: 6523.txt
>
>
> New cluster:
>  * Seeds: list of 6 internal IPs
>  * listen address: internal ip
>  * broadcast: external ip
> Two DC cluster, using GPFS where the external IPs are NATed.  Clusters fails to start with "Unable to contact any seeds!"
>  * Fail: Try to start a seed node
>  * Fail: Try to start two seed nodes at the same time in the same DC
>  * Success: Start two seed nodes at the same time in different DCs.
> Presumably related to CASSANDRA-5768


--
This message was sent by Atlassian JIRA
(v6.2#6252)