[
https://issues.apache.org/jira/browse/CASSANDRA-6523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007252#comment-14007252
]
Brandon Williams commented on CASSANDRA-6523:
---------------------------------------------
Part of the problem, is we can't know a seed's broadcast_address without, of
course, them gossiping it to us. We could possibly extend the 'talked to a
seed' check to loop through the endpoints we know about and look for a matching
broadcast_address, though that's a bit expensive and is kind of cheating since
we want to know we talked to a seed directly, not that we were told about a
seed, but I don't think that actually matters. I'll have to think about it
some.
bq. Barring a more clever check I suggest changing the message to something
like "Seed check failed! At least one boardcast_address must match IPs from
seed list".
Well, that's not entirely accurate either, since if you aren't using BCA at
all, it's confusing. We could print out the seeds with the error though, so at
least between that and the handshaking messages you'd get a clue.
> "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
>
> 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)
