[
https://issues.apache.org/jira/browse/MAPREDUCE-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259000#comment-13259000
]
Hadoop QA commented on MAPREDUCE-3812:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523665/MAPREDUCE-3812.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 5 new or modified test
files.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+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 failed these unit tests:
org.apache.hadoop.yarn.server.TestContainerManagerSecurity
org.apache.hadoop.yarn.server.resourcemanager.security.TestApplicationTokens
org.apache.hadoop.yarn.server.resourcemanager.TestClientRMService
org.apache.hadoop.yarn.server.resourcemanager.resourcetracker.TestNMExpiry
org.apache.hadoop.yarn.server.resourcemanager.TestAMAuthorization
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationACLs
org.apache.hadoop.mapred.TestClientRedirect
org.apache.hadoop.mapreduce.security.TestJHSSecurity
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2269//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2269//console
This message is automatically generated.
> Lower default allocation sizes, fix allocation configurations and document
> them
> -------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3812
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3812
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2, performance
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Harsh J
> Attachments: MAPREDUCE-3812-20120205.txt,
> MAPREDUCE-3812-20120206.1.txt, MAPREDUCE-3812-20120206.txt,
> MAPREDUCE-3812.patch, MAPREDUCE-3812.patch, MAPREDUCE-3812.patch,
> MAPREDUCE-3812.patch, MAPREDUCE-3812.patch
>
>
> After a few performance improvements tracked at MAPREDUCE-3561, like
> MAPREDUCE-3511 and MAPREDUCE-3567, even a 100K maps job can also run within
> 1GB vmem. We earlier increased AM slot size from 1 slot to two slots to work
> around the issues with AM heap. Now that those are fixed, we should go back
> to 1GB.
> This is just a configuration change.
> [P.s.]:
> - Currently min/max alloc is set at a per-scheduler config level, which makes
> no sense as there's no way to run multiple schedulers anyway. Switch configs
> to use a generic RM-config.
> - The min/max alloc configs aren't documented and we ought to document it
> (i.e. MAPREDUCE-4027)
> - 1 GB is perhaps too high for a slot's minimum. While job defaults can be
> left at such values, we should lower the minimum alloc to 128 MB to allow
> special requests of low memory out of the box itself. Shouldn't impact MR App
> in any way.
--
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
