[
https://issues.apache.org/jira/browse/HBASE-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278522#comment-13278522
]
Hudson commented on HBASE-5942:
-------------------------------
Integrated in HBase-0.92-security #107 (See
[https://builds.apache.org/job/HBase-0.92-security/107/])
HBASE-5942 HConnnectionManager.getRegionServerWithRetries doesn't call
afterCall properly (Revision 1335734)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
> HConnnectionManager.getRegionServerWithRetries doesn't call afterCall properly
> ------------------------------------------------------------------------------
>
> Key: HBASE-5942
> URL: https://issues.apache.org/jira/browse/HBASE-5942
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.1
> Reporter: Zhihong Yu
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.92.2
>
> Attachments: hbase-5942.patch
>
>
> HConnnectionManager.getRegionServerWithRetries:
> {code}
> return callable.call();
> } catch (Throwable t) {
> callable.shouldRetry(t);
> {code}
> shouldRetry relies on the proper startTime and endTime to calculate the
> timeout value. However, callable.afterCall() is called in finally block. Thus
> callable.callTimeout will be set to negative value in callable.shouldRetry().
--
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
