[YARN-10825] Yarn Service containers not getting killed after NM shutdown

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.1.1
• Component/s: yarn, yarn-native-services
• Assignee: D M Murali Krishna Reddy
• Reporter: Sushanta Sen
• Created: 17/Jun/21 11:06
• Updated: 29/Jun/21 05:08

Description

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.