cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Haddad (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14361) Allow SimpleSeedProvider to resolve multiple IPs per DNS name
Date Wed, 04 Apr 2018 15:31:00 GMT


Jon Haddad commented on CASSANDRA-14361:

I agree with you, you could *explicitly* put 1000 seeds in there.  Would you expect there
to be 1000 potential seeds in your gossip list by putting 1 thing in the seed list?  People
don't even mostly know about this behavior.  I'm not sure it's optimal, and I'm not arguing
against changing it, I'm just pointing it out and saying it's worth a discussion.  A point
against it being, the new behavior might be a bit surprising.

> Allow SimpleSeedProvider to resolve multiple IPs per DNS name
> -------------------------------------------------------------
>                 Key: CASSANDRA-14361
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Ben Bromhead
>            Assignee: Ben Bromhead
>            Priority: Minor
>             Fix For: 4.0
> Currently SimpleSeedProvider can accept a comma separated string of IPs or hostnames
as the set of Cassandra seeds. hostnames are resolved via InetAddress.getByName, which will
only return the first IP associated with an A, AAAA or CNAME record.
> By changing to InetAddress.getAllByName, existing behavior is preserved, but now Cassandra
can discover multiple IP address per record, allowing seed discovery by DNS to be a little
> Some examples of improved workflows with this change include: 
>  * specify the DNS name of a headless service in Kubernetes which will resolve to all
IP addresses of pods within that service. 
>  * seed discovery for multi-region clusters via AWS route53, AzureDNS etc
>  * Other common DNS service discovery mechanisms.
> The only behavior this is likely to impact would be where users are relying on the fact
that getByName only returns a single IP address.
> I can't imagine any scenario where that is a sane choice. Even when that choice has
been made, it only impacts the first startup of Cassandra and would not be on any critical

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message