[
https://issues.apache.org/jira/browse/CASSANDRA-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213066#comment-17213066
]
Andres de la Peña commented on CASSANDRA-14361:
-----------------------------------------------
Great, now it works perfectly.
Regarding the property to put in {{cassandra.yaml}} thresholds section, I meant
the new threshold
[{{seed_count_warn_threshold}}|https://github.com/apache/cassandra/blob/d4c92a3a90444b08a06fb3cf071d6c462aa04cd0/src/java/org/apache/cassandra/locator/SimpleSeedProvider.java#L36].
Having also that {{resolve_multiple_ip_addresses_per_dns_record}} flag is nice,
specially if this ends up merged in 4.0.x, which isn't a major version. As for
the naming and placement of the property, I'd say it suggests that it's a
global property that could be applied to any resolved IP, not only those of
seeds. IMO that could be perfectly valid if we want to use it in such way. If
we wanted to use it only to control the resolving of seeds I think we should
either add the "seeds" word to the name or, perhaps better, include it as one
of the {{parameters}} of the {{seed_provider}} section. WDYT?
> 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: [email protected]
For additional commands, e-mail: [email protected]
