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

Hadoop QA commented on YARN-3231:
---------------------------------

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

    {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:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6715//console

This message is automatically generated.

> FairScheduler changing queueMaxRunningApps on the fly will cause all pending 
> job stuck
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-3231
>                 URL: https://issues.apache.org/jira/browse/YARN-3231
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Siqi Li
>            Assignee: Siqi Li
>            Priority: Critical
>         Attachments: YARN-3231.v1.patch, YARN-3231.v2.patch
>
>
> When a queue is piling up with a lot of pending jobs due to the 
> maxRunningApps limit. We want to increase this property on the fly to make 
> some of the pending job active. However, once we increase the limit, all 
> pending jobs were not assigned any resource, and were stuck forever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to