hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3881) IPC client doesnt time out if far end handler hangs
Date Fri, 01 Aug 2008 16:40:32 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619069#action_12619069

Raghu Angadi commented on HADOOP-3881:

> If retry load is an issue then the whole client retry operations in [...]

The current implementation makes retry less relevant and not needed in most cases, right?
One of the main motivation was handle burst-y load gracefully at the server. BlockReports
do an exponential backoff right now, but it is not required and does not get triggered with
the current  IPC implementation. It needs to be removed.

We could add a FAQ entry in Wiki briefly stating that IPC calls don't timeout. 

> IPC client doesnt time out if far end handler hangs
> ---------------------------------------------------
>                 Key: HADOOP-3881
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3881
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: ipc
>            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.
You can reply to this email to add a comment to the issue online.

View raw message