hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4027) Document the minimum-allocation-mb and maximum-allocation-mb configurations
Date Sat, 21 Apr 2012 18:26:34 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258908#comment-13258908
] 

Hadoop QA commented on MAPREDUCE-4027:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12523637/MAPREDUCE-4027.patch
  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 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.TestFifoScheduler
                  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/2267//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2267//console

This message is automatically generated.
                
> Document the minimum-allocation-mb and maximum-allocation-mb configurations
> ---------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4027
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4027
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 0.23.3
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>         Attachments: MAPREDUCE-4027.patch, MAPREDUCE-4027.patch
>
>
> None of the current yarn.scheduler.fifo.minimum/maximum-allocation-mb and yarn.scheduler.capacity.minimum/maximum-allocation-mb
are documented anywhere. Without knowledge of these params, one can't change the default allocations.
And the default allocations are pretty high btw (MAPREDUCE-4026).
> We should document these in the Cluster Setup page at least.

--
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

        

Mime
View raw message