You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Miles Garnsey (Jira)" <ji...@apache.org> on 2021/04/14 07:07:00 UTC
[jira] [Commented] (CASSANDRA-14361) Allow SimpleSeedProvider to
resolve multiple IPs per DNS name
[ https://issues.apache.org/jira/browse/CASSANDRA-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320755#comment-17320755 ]
Miles Garnsey commented on CASSANDRA-14361:
-------------------------------------------
What is the status on this ticket? Can I be of any help? I have an interest in being able to use headless services in k8s to do discovery and this would be a big help.
I like [~adelapena]'s idea of making resolve_multiple_ip_addresses_per_dns_record a seed_provider section too, for what it is worth.
> Allow SimpleSeedProvider to resolve multiple IPs per DNS name
> -------------------------------------------------------------
>
> Key: CASSANDRA-14361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14361
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: Ben Bromhead
> Assignee: Ben Bromhead
> Priority: Low
> Fix For: 4.0.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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 easier.
> 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 path.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org