You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Zhihong Yu (Updated) (JIRA)" <ji...@apache.org> on 2012/02/01 18:35:00 UTC

[jira] [Updated] (HBASE-5310) HConnectionManager server cache key enhancement

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

Zhihong Yu updated HBASE-5310:
------------------------------

         Summary: HConnectionManager server cache key enhancement  (was: HConnectionManager cache server name enhancement)
    Hadoop Flags: Reviewed

Integrated to TRUNK.

Thanks for the patch Jimmy
                
> HConnectionManager server cache key enhancement
> -----------------------------------------------
>
>                 Key: HBASE-5310
>                 URL: https://issues.apache.org/jira/browse/HBASE-5310
>             Project: HBase
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 0.94.0
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>             Fix For: 0.94.0
>
>         Attachments: hbase-5310.txt
>
>
> HConnectionManager uses deprecated HServerAddress to create server cache key which needs to resolve the address every time.
> It should be better to use HRegionLocation.getHostnamePort() instead.
> In our cluster we have some DNS issue, resolving an address fails sometime which kills the application since it is a runtime
> exception IllegalArgumentException thrown at HServerAddress.getResolvedAddress.  This change will fix this issue as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira