hadoop-yarn-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] (YARN-1582) Capacity Scheduler: add a maximum-allocation-mb setting per queue
Date Thu, 29 Jan 2015 17:54:35 GMT

    [ https://issues.apache.org/jira/browse/YARN-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297235#comment-14297235

Hadoop QA commented on YARN-1582:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision fe2188a.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:red}-1 findbugs{color}.  The patch appears to introduce 1 new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:


Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6455//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/6455//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6455//console

This message is automatically generated.

> Capacity Scheduler: add a maximum-allocation-mb setting per queue 
> ------------------------------------------------------------------
>                 Key: YARN-1582
>                 URL: https://issues.apache.org/jira/browse/YARN-1582
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>    Affects Versions: 3.0.0, 0.23.10, 2.2.0
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>         Attachments: YARN-1582-branch-0.23.patch, YARN-1582.002.patch
> We want to allow certain queues to use larger container sizes while limiting other queues
to smaller container sizes.  Setting it per queue will help prevent abuse, help limit the
impact of reservations, and allow changes in the maximum container size to be rolled out more
> One reason this is needed is more application types are becoming available on yarn and
certain applications require more memory to run efficiently. While we want to allow for that
we don't want other applications to abuse that and start requesting bigger containers then
what they really need.  
> Note that we could have this based on application type, but that might not be totally
accurate either since for example you might want to allow certain users on MapReduce to use
larger containers, while limiting other users of MapReduce to smaller containers.

This message was sent by Atlassian JIRA

View raw message