hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chang Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state
Date Thu, 07 May 2015 22:42:01 GMT

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

Chang Li commented on YARN-2421:
--------------------------------

updated my patch, the current approach ignores allocate requests when app attempt is in final_saving,
finishing or isAppFinalStateStored

> 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: YARN-2421.4.patch, 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)

Mime
View raw message