Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 14 Feb 2014 00:26:20 +0000 (UTC)
From: "Rishit Shroff (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12630425.1359746643359.40230.1392337580035@arcas>
In-Reply-To: <JIRA.12630425.1359746643359@arcas>
References: <JIRA.12630425.1359746643359@arcas>
Subject: [jira] [Assigned] (HBASE-7737) [89-fb] Force to generate the
 hostAddress:port as stringValue in HServerAddress
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rishit Shroff reassigned HBASE-7737:
------------------------------------

    Assignee: Rishit Shroff

> [89-fb] Force to generate the hostAddress:port as stringValue in HServerAddress
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-7737
>                 URL: https://issues.apache.org/jira/browse/HBASE-7737
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: Rishit Shroff
>            Assignee: Rishit Shroff
>            Priority: Trivial
>
> There is a serious bug in HServerAddress, who depends on the stringValue [class variable] for comparison. This variable is supposed to be host_ip_address:port. 
> However, there is one constructor which allows user to pass a string as host_ip_address directly. This constructor is buggy because some caller may pass the host name instead of host ip address. And we found out one case in the HBase client.
> The fix is to normalize the stringValue generation by calling the existing function getHostAddressWithPort.
> For example:
> this.stringValue = getHostAddressWithPort();


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)