[
https://issues.apache.org/jira/browse/CASSANDRA-6523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005965#comment-14005965
]
Chris Burroughs commented on CASSANDRA-6523:
--------------------------------------------
Still present in 2.0.x series. There are a variety of stack overflow and
mailing list threads threads with "Unable to contact any seeds".
I think the problem is that CASSANDRA-5768 isn't checking "have I contacted a
seed" but "am I connected to one of these IP addresses". That ends up being
requirement that the seeds/broadcast/listen address line up in a particular way.
> "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
>
> 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)
