hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5493) In-memory map outputs can be leaked after shuffle completes
Date Tue, 03 Sep 2013 22:47:54 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Lowe updated MAPREDUCE-5493:
----------------------------------

    Attachment: MAPREDUCE-5493.patch

Patch to clear the various output sets after their contents have been added to the corresponding
array lists in the close() method.
                
> 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
>         Attachments: 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

Mime
View raw message