cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-10408) NodeProbe (NodeTool) getEndpoint always return null
Date Tue, 29 Sep 2015 18:46:05 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carl Yeksigian resolved CASSANDRA-10408.
----------------------------------------
    Resolution: Duplicate

Thank you for the detailed bug report!

This was the root cause of CASSANDRA-10382, and was fixed in that ticket.

> NodeProbe (NodeTool) getEndpoint always return null
> ---------------------------------------------------
>
>                 Key: CASSANDRA-10408
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10408
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: amnon heiman
>            Priority: Minor
>
> The NodeProbe getEndpoint implementation was changed to use the getHostIdToEndpoint map
with the host id.
> There is a confusion between the keys and value. The search here should have been a reverse
lookup - in the map the host ids are the values not the keys.
> The end result is that getEndpoint() will always return null, as a result getDataCenter
will be call the EndpointSnitchInfo getDatacenter with null, which will be equivalent to call
it with the loopback address, in that case either fix the getEndpoint implementation, or drop
it completely and use the loopback address to begin with.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message