hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-3881) IPC client doesnt time out if far end handler hangs
Date Tue, 06 Mar 2012 15:39:58 GMT

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

Steve Loughran updated HADOOP-3881:

    Affects Version/s: 1.0.0
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message