[YARN-9192] Deletion Taks will be picked up to delete running containers

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.9.1
• Component/s: applications
• Assignee: Unassigned
• Reporter: Sihai Ke
• Created: 11/Jan/19 13:13
• Updated: 21/Sep/20 15:17

Description

I suspect there is a bug in Yarn deletion task service, below is my repo steps:

1. First let's set yarn.nodemanager.delete.debug-delay-sec=3600, that means when the app finished, the Binary/container folder will be deleted after 3600 seconds.
2. when the application App1 (long running service) is running on machine machine1, and machine1 shutdown, ContainerManagerImpl#serviceStop() will be called -> ContainerManagerImpl#cleanUpApplicationsOnNMShutDown, and ApplicationFinishEvent will be sent, and then some delection tasks will be created, but be stored in DB and will be picked up to execute 3600 seconds.
3. 100 seconds later, machine1 comes back, and the same app is assigned to run this this machine, container created and works well.
4. then deleting task created in step 2 will be picked up to delete containers created in step 3 later.