Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 8 Jun 2016 15:24:21 +0000 (UTC)
From: "Adam Holmberg (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12976900.1465399460000.28076.1465399461105@Atlassian.JIRA>
In-Reply-To: <JIRA.12976900.1465399460000@Atlassian.JIRA>
References: <JIRA.12976900.1465399460000@Atlassian.JIRA> <JIRA.12976900.1465399460112@arcas>
Subject: [jira] [Created] (CASSANDRA-11979) cqlsh copyutil should get host
 metadata by connected address
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 08 Jun 2016 15:24:23 -0000

Adam Holmberg created CASSANDRA-11979:
-----------------------------------------

             Summary: 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
            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)