[jira] [Updated] (YARN-10825) Yarn Service containers not getting killed after NM shutdown

["D M Murali Krishna Reddy (Jira)" <ji...@apache.org>]

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

D M Murali Krishna Reddy updated YARN-10825:
--------------------------------------------
    Component/s: yarn-native-services

> Yarn Service containers not getting killed after NM shutdown
> ------------------------------------------------------------
>
>                 Key: YARN-10825
>                 URL: https://issues.apache.org/jira/browse/YARN-10825
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn, yarn-native-services
>    Affects Versions: 3.1.1
>            Reporter: Sushanta Sen
>            Assignee: D M Murali Krishna Reddy
>            Priority: Major
>
> When yarn.nodemanager.recovery.supervised is enabled and NM is shutdown, the new containers are getting launched after the RM sends the node lost event to AM, but the existing containers on the lost node are not getting killed. The issue has occurred only for yarn service. For Normal jobs the behavior is working fine.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org