[ https://issues.apache.org/jira/browse/CASSANDRA-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677984#comment-17677984 ]
Stefan Miklosovic edited comment on CASSANDRA-14361 at 1/17/23 9:13 PM: ------------------------------------------------------------------------ Both runs (yours too) look good to me. I ll merge this (1) (1) https://github.com/instaclustr/cassandra/commit/69113b85f94bd3d4e23cd119fac8de782e2d914e was (Author: smiklosovic): Both runs (yours too) looks good tome. I ll merge this (1) (1) https://github.com/instaclustr/cassandra/commit/69113b85f94bd3d4e23cd119fac8de782e2d914e > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org