[
https://issues.apache.org/jira/browse/HBASE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243665#comment-13243665
]
Lars Hofhansl commented on HBASE-5682:
--------------------------------------
bq. You think this should go into 0.92?
Probably. I guess most folks have clients that they restart frequently, use
thrift, or asynchhbase. But in its current form using the standard HBase client
in an app server is very error prone if the HBase/ZK cluster is ever serviced
without bringing the app server down in lock step.
bq. Didn't we add a check for if the connection is bad?
Yeah with hbase-5153 but in 0.90 only. At some point we decided the fix there
wasn't good and Ram patched it up for 0.90.
This should subsime HBASE-5153. I'm happy to even put this in 0.90, but that's
up to Ram.
bq. I'm interested in problems you see in hbase-5153 or issues you have w/ the
implementation there that being the 0.96 client.
What I saw in 0.96 is that the client was blocked for a very long time (gave up
after a few minutes), even though I had set all timeouts to low values. This is
also deadly in an app server setting. Might be a simple fix there, didn't dig
deeper.
> 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
> Priority: Critical
> Fix For: 0.94.0
>
> Attachments: 5682-all-v2.txt, 5682-all.txt, 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
