hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7121) Exceptions while serializing IPC call response are not handled well
Date Wed, 01 Jun 2011 09:45:47 GMT

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

Hudson commented on HADOOP-7121:
--------------------------------

Integrated in Hadoop-Common-22-branch #59 (See [https://builds.apache.org/hudson/job/Hadoop-Common-22-branch/59/])
    HADOOP-7121. Exceptions while serializing IPC call responses are not handled well. Contributed
by Todd Lipcon.

todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1129983
Files : 
* /hadoop/common/branches/branch-0.22/src/java/org/apache/hadoop/ipc/Server.java
* /hadoop/common/branches/branch-0.22/src/test/core/org/apache/hadoop/ipc/TestIPC.java
* /hadoop/common/branches/branch-0.22/CHANGES.txt


> 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, hadoop-7121.txt, 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

Mime
View raw message