[
https://issues.apache.org/jira/browse/MAPREDUCE-5493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769430#comment-13769430
]
Hudson commented on MAPREDUCE-5493:
-----------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #335 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/335/])
MAPREDUCE-5493. Cleanup in-memory & on-disk segments to prevent leak on shuffle
completion. Contributed by Jason Lowe. (acmurthy:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1523660)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/MergeManagerImpl.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapreduce/task/reduce/TestMerger.java
> In-memory map outputs can be leaked after shuffle completes
> -----------------------------------------------------------
>
> Key: MAPREDUCE-5493
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5493
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.1.0-beta, 0.23.9
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Blocker
> Fix For: 2.1.1-beta
>
> Attachments: MAPREDUCE-5493-branch-0.23.patch, MAPREDUCE-5493.patch
>
>
> MergeManagerImpl#close adds the contents of inMemoryMergedMapOutputs and
> inMemoryMapOutputs to a list of map outputs that is subsequently processed,
> but it does not clear those sets. This prevents some of the map outputs from
> being garbage collected and significantly reduces the memory available for
> the subsequent reduce phase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira