[
https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546724#comment-14546724
]
Hudson commented on YARN-2421:
------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #929 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/929/])
YARN-2421. RM still allocates containers to an app in the FINISHING state.
Contributed by Chang Li (jlowe: rev f7e051c4310024d4040ad466c34432c72e88b0fc)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestApplicationMasterService.java
* hadoop-yarn-project/CHANGES.txt
> RM 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
> Reporter: Thomas Graves
> Assignee: Chang Li
> Fix For: 2.8.0
>
> Attachments: YARN-2421.4.patch, YARN-2421.5.patch, YARN-2421.6.patch,
> YARN-2421.7.patch, YARN-2421.8.patch, YARN-2421.9.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)
