hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions
Date Sun, 04 Dec 2011 02:02:40 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162255#comment-13162255

Hadoop QA commented on HBASE-4936:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/435//console

This message is automatically generated.
> 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
>         Attachments: 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, - 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


View raw message