[
https://issues.apache.org/jira/browse/YARN-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295372#comment-14295372
]
Hadoop QA commented on YARN-3057:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12695003/YARN-3057.2.patch
against trunk revision 9850e15.
{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:green}+1 findbugs{color}. The patch does not introduce any 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:
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6436//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6436//console
This message is automatically generated.
> Need update apps' runnability when reloading allocation files for
> FairScheduler
> -------------------------------------------------------------------------------
>
> Key: YARN-3057
> URL: https://issues.apache.org/jira/browse/YARN-3057
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Reporter: Jun Gong
> Assignee: Jun Gong
> Attachments: YARN-3057.2.patch, YARN-3057.patch
>
>
> If we submit a app and the number of running app in its corresponding leaf
> queue has reached its max limit, the app will be put into 'nonRunnableApps'.
> And its runnabiltiy will only be updated when removing a
> appattempt(FairScheduler will call `updateRunnabilityOnAppRemoval` at that
> time).
> Suppose there are only service apps running, they will not finish, so the
> submitted app will not be scheduled even we change leaf queue's max limit. I
> think we need update apps' runnability when reloading allocation files for
> FairScheduler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
