[
https://issues.apache.org/jira/browse/HBASE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051631#comment-13051631
]
Karthick Sankarachary commented on HBASE-4003:
----------------------------------------------
bq. What do you think the implications of notifyAll on everything were Karthick?
Basically, it would notify all calls, even those that may have arrived less
than the timeout period ago. that they timed out. FWIW, if you don't use
timeouts, then you won't run into this issue.
> 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.90.4
>
> Attachments: 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
