hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6606) Test for reconnecting with HBaseAdmin using unmanaged HConnection
Date Thu, 23 Aug 2012 23:40:43 GMT

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

Hudson commented on HBASE-6606:

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #144 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/144/])
    HBASE-6606 Test for reconnecting with HBaseAdmin using unmanaged HConnection (Revision

     Result = FAILURE
stack : 
Files : 
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java

> Test for reconnecting with HBaseAdmin using unmanaged HConnection
> -----------------------------------------------------------------
>                 Key: HBASE-6606
>                 URL: https://issues.apache.org/jira/browse/HBASE-6606
>             Project: HBase
>          Issue Type: Task
>          Components: client, test
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>            Priority: Minor
>             Fix For: 0.96.0
>         Attachments: HBASE-6606.patch, HBASE-6606-v2.patch
> HBASE-5058 allowed HBaseAdmin to work with an existing and unmanaged HConnection.  The
retry semantics of managed vs unmanaged connections are different.  From the JIRA:
> "For an HConnection that is passed from the outside, it has to be possible to try again.
So if the HConnection is managed we retain the old behavior (i.e. only try once, give up after
that, even if that failed).
> For an unmanaged connection we try again unless we actually found a master. ."
> I couldn't find any test of this behavior, only that the HBaseAdmin works with an unmanaged
connection, i.e. no retry testing.

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