[
https://issues.apache.org/jira/browse/CASSANDRA-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677698#comment-17677698
]
Stefan Miklosovic commented on CASSANDRA-14361:
-----------------------------------------------
As CASSANDRA-18152 is done we can return to this. I am running the builds here
(1,2)
The only question I have is if we want to have this enabled by default. I am
sorry if I missed this but I dont see this decided anywhere. I can imagine this
might be primarily used in environments like Kubernetes etc which are quite
specific and I do not feel like enabling this by default is good idea, at least
from "compatibility" point of view. People can explicitly opt-in if they wish
and it scratches their itch.
Ideas? [~adelapena] [~jkoppenhofer] [~benbromhead]
(1)
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1732/workflows/7048d707-5515-4a05-8dcc-6a026cfe0b6d
(2)
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1732/workflows/5df1cd83-f92f-4857-b383-a69e9bd2217c
> 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: Stefan Miklosovic
> Priority: Low
> Fix For: 4.x
>
> Time Spent: 1h 20m
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
