You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2012/12/12 00:09:29 UTC
[jira] [Commented] (HBASE-7170) [0.94 branch] Allow
HConnectionImplementation to reconnect to master multiple times
[ https://issues.apache.org/jira/browse/HBASE-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529435#comment-13529435 ]
Hudson commented on HBASE-7170:
-------------------------------
Integrated in HBase-0.94-security #86 (See [https://builds.apache.org/job/HBase-0.94-security/86/])
HBASE-7170 Allow HConnectionImplementation to reconnect to master multiple times (Revision 1410622)
Result = SUCCESS
gchanan :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
* /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
> [0.94 branch] Allow HConnectionImplementation to reconnect to master multiple times
> -----------------------------------------------------------------------------------
>
> Key: HBASE-7170
> URL: https://issues.apache.org/jira/browse/HBASE-7170
> Project: HBase
> Issue Type: Task
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Priority: Minor
> Fix For: 0.94.4
>
> Attachments: HBASE-7170.patch
>
>
> HBASE-5058 retained the old behavior of managed HConnections not retrying their connection to master b/c of the "masterChecked" variable.
> This behavior isn't great though, because you can get in the following situation:
> 1) Connect to master using HBaseAdmin
> 2) Master goes down
> 3) New master takes over
> 4) The HBaseAdmin object is now useless
> The client needs to create a new HBaseAdmin in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira