[jira] [Comment Edited] (HBASE-9739) HBaseClient does not behave nicely when the called thread is interrupted

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

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

Lars Hofhansl edited comment on HBASE-9739 at 10/10/13 4:21 AM:
----------------------------------------------------------------

At second inspection it looks like this should be correct. sendParam is called from another thread (not the Connection's thread), but the Connection's thread does the right thing in the run() loop - it closes the connection. The next call to call(...) in HBaseClient should then get a new connection.

I'll do some more checking on our side on how exactly we got ourselves into this.

[~giacomotaylor], FYI


was (Author: lhofhansl):
At second inspection it looks like this should be correct. sendParam is called from another thread (not the Connection's thread), but the Connection's thread does the right thing in the run() loop - it closes the connection. The next call to call(...) in HBaseClient should then get a new connection.

I'll do some more checking on our side on how exactly we got ourselves into this.

[~giacomotaylor]

> HBaseClient does not behave nicely when the called thread is interrupted
> ------------------------------------------------------------------------
>
>                 Key: HBASE-9739
>                 URL: https://issues.apache.org/jira/browse/HBASE-9739
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>
> Just ran into a scenario where HBaseClient became permanently useless after we interrupted the using thread.
> The problem is here:
> {code}
>       } catch(IOException e) {
>         markClosed(e);
> {code}
> In sendParam(...).
> If the IOException is caused by an interrupt we should not close the connection.



--
This message was sent by Atlassian JIRA
(v6.1#6144)