[
https://issues.apache.org/jira/browse/HBASE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243021#comment-13243021
]
Lars Hofhansl commented on HBASE-5682:
--------------------------------------
The gist of this change is that (1) the ZK connection is re-checked in all
calls where it is needed and re-established if needed and (2) if the connection
is down the client can find out quickly (by setting timeouts accordingly) and
report via IOException to the calling thread.
This is only done for unmanaged HConnections (those that were created with
HConnectionManager.createConnection(...) and are hence not reference counted.
Reference counted HConnctions are treated as before.)
This is needed to safely use the HConnection is a multithreaded long-lived
AppServer setting.
(In my tests I found that even 0.96 needs some more work here, but that's for a
different jira.)
> Allow HConnectionImplementation to recover from ZK connection loss (for 0.94
> only)
> ----------------------------------------------------------------------------------
>
> Key: HBASE-5682
> URL: https://issues.apache.org/jira/browse/HBASE-5682
> Project: HBase
> Issue Type: Improvement
> Components: client
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.94.1
>
> Attachments: 5682-v2.txt, 5682.txt
>
>
> Just realized that without this HBASE-4805 is broken.
> I.e. there's no point keeping a persistent HConnection around if it can be
> rendered permanently unusable if the ZK connection is lost temporarily.
> Note that this is fixed in 0.96 with HBASE-5399 (but that seems to big to
> backport)
--
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
