You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Lin Yang (JIRA)" <ji...@apache.org> on 2010/05/18 04:57:04 UTC
[jira] Commented: (HADOOP-6768) RPC client can response more
efficiently when sendParam() got IOException
[ https://issues.apache.org/jira/browse/HADOOP-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868499#action_12868499 ]
Lin Yang commented on HADOOP-6768:
----------------------------------
又看见师兄提bug了...
--
杨林
http://blog.csdn.net/idning
> RPC client can response more efficiently when sendParam() got IOException
> -------------------------------------------------------------------------
>
> Key: HADOOP-6768
> URL: https://issues.apache.org/jira/browse/HADOOP-6768
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.22.0
> Reporter: Xiao Kang
> Fix For: 0.22.0
>
>
> Under current RPC client implementation, when Client.Connection.sendParam() encounters IOException it just marks the exception and wait receiveResponse() thread to handle the exception. However, receiveResponse() may block ipc.ping.interval on socket read().
> This means that RPC client may wait ipc.ping.interval(typically 1 miniute) when exception in sendParam().
> It maybe not so reasonable in some situation. For example using "hadoop fs -put " a small file, DFSClient.close() will interupt renewLease() thread and it may wait 1 minute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.