[
https://issues.apache.org/jira/browse/CASSANDRA-11979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327058#comment-15327058
]
Stefania commented on CASSANDRA-11979:
--------------------------------------
Thanks, once the driver version 3.5 is available, we will update the cqlsh
bundled driver in 2.2+ and replace all occurrences of {{shell.hostname}} with
{{shell.conn.control_connection.host}}.
> cqlsh copyutil should get host metadata by connected address
> ------------------------------------------------------------
>
> Key: CASSANDRA-11979
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11979
> Project: Cassandra
> Issue Type: Bug
> Reporter: Adam Holmberg
> Assignee: Stefania
> Priority: Minor
> Fix For: 2.2.x, 3.x
>
>
> pylib.copyutil presently accesses cluster metadata using {{shell.hostname}}
> which could be an unresolved hostname.
> https://github.com/apache/cassandra/blob/58d3b9a90461806d44dd85bf4aa928e575d5fb6c/pylib/cqlshlib/copyutil.py#L207
> Cluster metadata normally refers to hosts in terms of numeric host address,
> not hostname. This works in the current integration because the driver allows
> hosts with unresolved names into metadata during the initial control
> connection. In a future version of the driver, that anomaly is removed, and
> no duplicate hosts-by-name are present in the metadata.
> We will need to update copyutil to refer to hosts by address when accessing
> metadata. This can be accomplished by one of two methods presently:
> # shell.conn.control_connection.host (gives the current connected host
> address)
> # scan metadata.all_hosts() for the one that {{is_up}} and use
> host.address/host.datacenter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
