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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/06/01 02:40:47 UTC
[jira] [Updated] (HADOOP-7121) Exceptions while serializing IPC
call response are not handled well
[ https://issues.apache.org/jira/browse/HADOOP-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HADOOP-7121:
--------------------------------
Attachment: hadoop-7121.txt
Attached patch adds coverage to all parts of the IPC lifecycle:
- client side write param
- server side read param
- server side write response
- client side read response
In the cases that the error occurs server side, it sends back the exception to the client as well as logging it.
> Exceptions while serializing IPC call response are not handled well
> -------------------------------------------------------------------
>
> Key: HADOOP-7121
> URL: https://issues.apache.org/jira/browse/HADOOP-7121
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Labels: newbie
> Fix For: 0.22.0
>
> Attachments: hadoop-7121.txt
>
>
> We had a situation where for some reason the serialization of an RPC call's response was throwing OOME. When this happens, the exception is not caught, and the call never gets a response - the client just hangs. Additionally, the OOME propagated all the way to the top of the IPC handler and caused the handler. Plus, the Handler upon exit only logged to stdout and not to the log4j logs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira