[
https://issues.apache.org/jira/browse/CASSANALYTICS-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Johnson updated CASSANALYTICS-62:
----------------------------------------
Resolution: Workaround
Status: Resolved (was: Triage Needed)
Closing this in favour ofÂ
[#CASSIDECAR|https://github.com/apache/cassandra-sidecar/pull/227]. Happy to
reopen if there's a use-case outside of setting this on the sidecar.
> Support for using IP Address as Sidecar/Instance identifier
> -----------------------------------------------------------
>
> Key: CASSANALYTICS-62
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-62
> Project: Apache Cassandra Analytics
> Issue Type: Task
> Reporter: Andrew Johnson
> Assignee: Andrew Johnson
> Priority: Normal
>
> Cassandra Analytics currently uses the FQDN as the Sidecar/Instance
> identifier. There's a few cases where users may want to use the IP address of
> hosts as the identifier rather than FQDN.
> The proposed change is to have a flag which will allow using the address as
> the host identifier on network calls rather than the fqdn.
> This will also require changing `RingProvider.validateTaskTokenRangeMappings`.
> Alternatively, this could be handled by the Sidecar which could return the IP
> address as the FQDN when specified.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
