Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 22 Jun 2011 04:35:47 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <823805932.27345.1308717347379.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2072822346.17439.1308361667407.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4003) Cleanup Calls Conservatively On
 Timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053040#comment-13053040 ] 

stack commented on HBASE-4003:
------------------------------

@Karthick Do you want to update the patch then before I commit?

> 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