[
https://issues.apache.org/jira/browse/YARN-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539581#comment-16539581
]
Rohith Sharma K S commented on YARN-8473:
-----------------------------------------
+1 compiled on branch-2.8 and succeeded. The QA reports before patch failure
because of the compilation issue. After this patch, compilation is succeeded.
The javac error is unrelated to this patch.
Committing shorlty
> Containers being launched as app tears down can leave containers in NEW state
> -----------------------------------------------------------------------------
>
> Key: YARN-8473
> URL: https://issues.apache.org/jira/browse/YARN-8473
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.8.4
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Major
> Fix For: 2.10.0, 3.2.0, 3.1.1, 2.9.2, 2.8.5, 3.0.4
>
> Attachments: YARN-8473-branch-2.8.addendum.001.patch,
> YARN-8473.001.patch, YARN-8473.002.patch, YARN-8473.003.patch
>
>
> I saw a case where containers were stuck on a nodemanager in the NEW state
> because they tried to launch just as an application was tearing down. The
> container sent an INIT_CONTAINER event to the ApplicationImpl which then
> executed an invalid transition since that event is not handled/expected when
> the application is in the process of tearing down.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
