[
https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335575#comment-14335575
]
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/12700592/YARN-3231.v2.patch
against trunk revision 9a37247.
{color:red}-1 patch{color}. Trunk compilation may be broken.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6714//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)
