[
https://issues.apache.org/jira/browse/HBASE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242980#comment-13242980
]
Lars Hofhansl commented on HBASE-5682:
--------------------------------------
A little bit more background:
I put HBASE-4805 in place to be able to use the standard HBase client in long
running app server processes. The idea is that one can manage an HConnection
and a ThreadPool per app server and then cheaply create HTables when needed.
For that setup it is vital that the HConnection does not become unusable when
there are temporary network outages, or that HBase cluster is temporarily taken
down.
In that case the clients should timeout quickly to allow the application to
react to it, and if the network/cluster has recovered the application should be
able to recover.
> Add retry logic in HConnectionImplementation#resetZooKeeperTrackers (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.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
