[
https://issues.apache.org/jira/browse/HBASE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078978#comment-13078978
]
Hudson commented on HBASE-4003:
-------------------------------
Integrated in HBase-TRUNK #2075 (See
[https://builds.apache.org/job/HBase-TRUNK/2075/])
HBASE-4003 Cleanup Calls Conservatively On Timeout (Karthick)
tedyu :
Files :
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java
> Cleanup Calls Conservatively On Timeout
> ---------------------------------------
>
> Key: HBASE-4003
> URL: https://issues.apache.org/jira/browse/HBASE-4003
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.90.3
> Reporter: Karthick Sankarachary
> Assignee: Karthick Sankarachary
> Fix For: 0.92.0
>
> Attachments: HBASE-4003-V2.patch, HBASE-4003.patch
>
>
> In the event of a socket timeout, the {{HBaseClient}} iterates over the
> outstanding calls (on that socket), and notifies them that a
> {{SocketTimeoutException}} has occurred. Ideally, we should be cleanup up
> just those calls that have been outstanding for longer than the specified
> socket timeout.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira