[
https://issues.apache.org/jira/browse/CASSANDRA-6523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020303#comment-14020303
]
Chris Burroughs commented on CASSANDRA-6523:
--------------------------------------------
Jason, thanks for the suggestion. I think there are a very different ways I
could work around it. At this point though I'd like to see it cleared up so
others don't trip over it too.
Tested driftx's patch on top of 2.0.8 with two DCs and the same NAT setup.
* Started a node in DC A with auto_bootrap:false and it came up happy.
* Started a second node in DC A, and it successfully bootstrapped.
* Stopped all DC A nodes, started a node in DC B with auto_bootrap:true. It
failed with "Unable to contact any seeds!'
* Started all DC A nodes, nodes in B could bootstrap.
So it looks like it works from my point of view.
> "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: 2.1.0
>
> 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)
