[
https://issues.apache.org/jira/browse/MAPREDUCE-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287629#comment-13287629
]
Hadoop QA commented on MAPREDUCE-4301:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12530589/MR-4301.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2431//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2431//console
This message is automatically generated.
> Dedupe some strings in MRAM for memory savings
> ----------------------------------------------
>
> Key: MAPREDUCE-4301
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4301
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: applicationmaster
> Affects Versions: 0.23.3, 2.0.0-alpha
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Attachments: MR-4301.txt
>
>
> Recently an OutOfMemoryError caused one of our jobs to become a zombie
> (MAPREDUCE-4300). It was a rather large job with 78000+ map tasks and only
> 750MB of heap configured. I took a heap dump to see if there were any
> obvious memory leaks, and I could not find any, but yourkit and some digging
> found some potential memory optimizations that we could do.
> In this particular case we could save about 20MB if
> SplitMetaInfoReader.readSplitMetaInfo only computed the JobSplitFile once
> instead of for each split. (a 2 line change)
> I will look into some others and see if there are more savings I can come up
> with.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
