hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3893) allow capacity scheduler configs maximum-applications and maximum-am-resource-percent configurable on a per queue basis
Date Fri, 02 Mar 2012 23:59:58 GMT

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

Hadoop QA commented on MAPREDUCE-3893:
--------------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12516901/MAPREDUCE-3893-1.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +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 passed unit tests in .

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1990//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1990//console

This message is automatically generated.
                
> allow capacity scheduler configs maximum-applications and maximum-am-resource-percent
configurable on a per queue basis
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3893
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3893
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Thomas Graves
>            Assignee: Eric Payne
>            Priority: Critical
>         Attachments: MAPREDUCE-3893-1.txt
>
>
> The capacity scheduler configs for  maximum-applications and maximum-am-resource-percent
are currently configured globally and then made proportional to each queue based on its capacity.
There are times when this may not work well.  some exampless -  if you have a queue that is
running on uberAM jobs, the jobs a queue is running always has a small number of containers,
and then you have the opposite where in a queue with very small capacity, you may want to
limit the am resources even more so you don't end up deadlocked with all your capacity being
used for app masters.
> I think we should make those configurable on a per queue basis.

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