You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/09/01 23:05:47 UTC

[jira] [Updated] (YARN-3231) FairScheduler: Changing queueMaxRunningApps interferes with pending jobs

     [ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated YARN-3231:
------------------------------------------
    Fix Version/s: 2.6.1

Pulled this into 2.6.1. Ran compilation and TestFairScheduler before the push. Patch applied cleanly.

> FairScheduler: Changing queueMaxRunningApps interferes with pending jobs
> ------------------------------------------------------------------------
>
>                 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
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.0, 2.6.1
>
>         Attachments: YARN-3231.v1.patch, YARN-3231.v2.patch, YARN-3231.v3.patch, YARN-3231.v4.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)