hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6833) IPC leaks call parameters when exceptions thrown
Date Tue, 22 Jun 2010 03:20:55 GMT

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

Todd Lipcon commented on HADOOP-6833:
-------------------------------------

I think the "new warnings" are because I used UTF8 in the test, and UTF8 is deprecated. I
used it to follow the pattern elsewhere in the test. Let me know if I should change the test
case to use something like Text or LongWritable instead.

> IPC leaks call parameters when exceptions thrown
> ------------------------------------------------
>
>                 Key: HADOOP-6833
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6833
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.20.2, 0.21.0, 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>         Attachments: hadoop-6833.txt
>
>
> HADOOP-6498 moved the calls.remove() call lower into the SUCCESS clause of receiveResponse(),
but didn't put a similar calls.remove into the ERROR clause. So, any RPC call that throws
an exception ends up orphaning the Call object in the connection's "calls" hashtable. This
prevents cleanup of the connection and is a memory leak for the call parameters.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message