[
https://issues.apache.org/jira/browse/HBASE-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-4087:
--------------------------
Attachment: 4087.txt
4087.txt
First attempt at solving this issue.
When connection.getMaster() throws UndeclaredThrowableException (corresponding
to Connection refused error), we close the stale connection and reestablish new
connection.
I have to declare HBaseAdmin.connection as not final.
TestMasterRestartAfterDisablingTable (from HBASE-4052) passes with this patch.
> HConnectionManager should perform validation of connection it hands out
> -----------------------------------------------------------------------
>
> Key: HBASE-4087
> URL: https://issues.apache.org/jira/browse/HBASE-4087
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Priority: Critical
> Fix For: 0.92.0
>
> Attachments: 4087.txt
>
>
> Through HBASE-3777, HConnectionManager reuses the connection to HBase servers.
> One challenge, discovered in troubleshooting HBASE-4052, is how we invalidate
> connection(s) to server which gets restarted.
> There're at least two ways.
> 1. HConnectionManager utilizes background thread(s) to periodically perform
> validation of connections in HBASE_INSTANCES and remove stale connection(s).
> 2. Allow HBaseClient (including HBaseAdmin) to provide feedback to
> HConnectionManager.
> The solution can be a combination of both of the above.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
