[
https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164284#comment-13164284
]
Hudson commented on HBASE-4936:
-------------------------------
Integrated in HBase-TRUNK-security #24 (See
[https://builds.apache.org/job/HBase-TRUNK-security/24/])
HBASE-4936 Cached HRegionInterface connections crash when getting
UnknownHost exceptions
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/catalog/CatalogTracker.java
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
> Key: HBASE-4936
> URL: https://issues.apache.org/jira/browse/HBASE-4936
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.92.0
> Reporter: Andrei Dragomir
> Assignee: Andrei Dragomir
> Fix For: 0.94.0
>
> Attachments: HBASE-4936-v2.patch, HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for
> development, the following thing happens:
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname
> (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different
> (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an
> UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn),
> uncaught in the catch statements. The server will crash constantly.
> The error should be caught and not rethrown, so that the cached connection
> expires normally.
--
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
