[
https://issues.apache.org/jira/browse/HADOOP-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067278#comment-13067278
]
Luke Lu commented on HADOOP-6833:
---------------------------------
Thanks for the +1 for branch-0.20-security, Owen, I'll cherry-pick the change
and run some test.
> 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
> Fix For: 0.20.3, 0.20.205.0, 0.21.1, 0.22.0
>
> Attachments: hadoop-6833-20.patch, hadoop-6833.txt, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
