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-853) maximum-am-resource-percent doesn't work consistently with refreshQueues
Date Thu, 20 Jun 2013 07:22:20 GMT

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

Hadoop QA commented on YARN-853:
--------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12588770/YARN-853.patch
  against trunk revision .

    {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}.  The javadoc tool did not generate any 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
1.3.9) warnings.

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

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

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

This message is automatically generated.
                
> maximum-am-resource-percent doesn't work consistently with refreshQueues
> ------------------------------------------------------------------------
>
>                 Key: YARN-853
>                 URL: https://issues.apache.org/jira/browse/YARN-853
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 3.0.0, 2.1.0-beta, 2.0.5-alpha
>            Reporter: Devaraj K
>            Assignee: Devaraj K
>         Attachments: YARN-853.patch
>
>
> If we update yarn.scheduler.capacity.maximum-am-resource-percent / yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent
configuration and then do the refreshNodes, it uses the new config value to calculate Max
Active Applications and Max Active Application Per User. If we add new node after issuing
 'rmadmin -refreshQueues' command, it uses the old maximum-am-resource-percent config value
to calculate Max Active Applications and Max Active Application Per User. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message