hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cosmin Lehene (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7013) Avoid reusing a input stream that stumbles on rpc-timeout in HBaseClient
Date Thu, 08 Jan 2015 08:55:35 GMT

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

Cosmin Lehene commented on HBASE-7013:

[~ikeda], [~apurtell] client has changed a bit. Is this still valid?

> Avoid reusing a input stream that stumbles on rpc-timeout in HBaseClient
> ------------------------------------------------------------------------
>                 Key: HBASE-7013
>                 URL: https://issues.apache.org/jira/browse/HBASE-7013
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>            Reporter: Hiroshi Ikeda
>              Labels: delete
> HBASE-2937 introduces rpc-timeout and sets SO_TIMEOUT parameter of the socket to throw
SocketTimeoutException. That means the exception can be thrown from any code that reads data
directly/indirectly from the socket. If the exception is thrown in the middle of reading a
set of data, it is required to drag out and drop the rest part of the set of data from the
socket and make ready to read the next data, in order to reuse the socket. It seems difficult,
and I can't find such recovering code in HBaseClient.
> I think, when IO streams wrapping the socket throw an exception, the nesting connection
instance should be discarded, and rpc-timeout should be handled separately from SO_TIMEOUT

This message was sent by Atlassian JIRA

View raw message