[jira] [Updated] (HBASE-7170) [0.94 branch] Allow HConnectionImplementation to reconnect to master multiple times

["Gregory Chanan (JIRA)" <ji...@apache.org>]

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

Gregory Chanan updated HBASE-7170:
----------------------------------

    Attachment: HBASE-7170.patch

Here's a patch that illustrates the problem and fixes it.

This backports HBASE-6606 (the testUnmanagedHConnectionReconnect test in TestFromClientSide) to 0.94.  The test causes the master to die and a new master to come back up in TestFromClientSide.

But due to HBASE-5051, all the tests in TestFromClientSide use the same HBaseAdmin, so all the tests that are executed after testUnmanagedHConnectionReconnect fail.
                
> [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