cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6523) "Unable to contact any seeds!" with multi-DC cluster and listen != broadcast address
Date Thu, 22 May 2014 21:45:02 GMT

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

Brandon Williams commented on CASSANDRA-6523:
---------------------------------------------

It's comparing the actual IP address it received contact from to the seed list, so if it's
being contacted by the broadcast address, but the seed is listed with the internal address,
there won't be a match.  So, you'd probably want a different seed list for DC 1 and DC 2,
with the listen/broadcast switched for the seeds that aren't local.

> "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
>
> 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)

Mime
View raw message