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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2018/07/02 17:54:00 UTC

[jira] [Updated] (YARN-8473) Containers being launched as app tears down can leave containers in NEW state

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

Jason Lowe updated YARN-8473:
-----------------------------
    Attachment: YARN-8473.001.patch

> 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
>         Attachments: YARN-8473.001.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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org