[YARN-1922] Process group remains alive after container process is killed externally

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.6.0
• Component/s: nodemanager

Environment

CentOS 6.4

• Hadoop Flags: Reviewed
• Assignee: Billie Rinaldi
• Reporter: Billie Rinaldi
• Created: 10/Apr/14 17:24
• Updated: 18/May/15 13:31
• Resolved: 04/Nov/14 00:48

Description

If the main container process is killed externally, ContainerLaunch does not kill the rest of the process group. Before sending the event that results in the ContainerLaunch.containerCleanup method being called, ContainerLaunch sets the "completed" flag to true. Then when cleaning up, it doesn't try to read the pid file if the completed flag is true. If it read the pid file, it would proceed to send the container a kill signal. In the case of the DefaultContainerExecutor, this would kill the process group.

Issue Links

• blocks: SLIDER-599 When application is created as user hdfs need to call destroy twice to delete the hdfs folder for the app