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 "Chen He (JIRA)" <ji...@apache.org> on 2015/01/08 19:15:35 UTC

[jira] [Updated] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

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

Chen He updated YARN-2421:
--------------------------
    Target Version/s: 2.7.0  (was: 2.6.0)

> CapacityScheduler still allocates containers to an app in the FINISHING state
> -----------------------------------------------------------------------------
>
>                 Key: YARN-2421
>                 URL: https://issues.apache.org/jira/browse/YARN-2421
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.4.1
>            Reporter: Thomas Graves
>            Assignee: chang li
>         Attachments: yarn2421.patch, yarn2421.patch, yarn2421.patch
>
>
> I saw an instance of a bad application master where it unregistered with the RM but then continued to call into allocate.  The RMAppAttempt went to the FINISHING state, but the capacity scheduler kept allocating it containers.   We should probably have the capacity scheduler check that the application isn't in one of the terminal states before giving it containers. 



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