You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/18 22:06:09 UTC

[jira] [Resolved] (HADOOP-3881) IPC client doesnt time out if far end handler hangs

     [ https://issues.apache.org/jira/browse/HADOOP-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved HADOOP-3881.
--------------------------------------

    Resolution: Incomplete

Closing this as stale.

> IPC client doesnt time out if far end handler hangs
> ---------------------------------------------------
>
>                 Key: HADOOP-3881
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3881
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 1.0.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> This is what appears to be happening in some changes of mine that (inadventently) blocked JobTracker: if the client can connect to the far end and invoke an operation, the far end has forever to deal with the request: the client blocks too.
> Clearly the far end shouldn't do this; its a serious problem to address. but should the client hang? Should it not time out after some specifiable time and signal that the far end isn't processing requests in a timely manner? 
> (marked as minor as this shouldn't arise in day to day operation. but it should be easy to create a mock object to simulate this, and timeouts are considered useful in an IPC)



--
This message was sent by Atlassian JIRA
(v6.2#6252)