[
https://issues.apache.org/jira/browse/YARN-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi updated YARN-1922:
---------------------------------
Attachment: YARN-1922.2.patch
The new patch adds a test. If the test is run without the change to
ContainerLaunch, the test fails and a child process is left running. The test
passes when the change to ContainerLaunch is applied.
> Process group remains alive after container process is killed externally
> ------------------------------------------------------------------------
>
> Key: YARN-1922
> URL: https://issues.apache.org/jira/browse/YARN-1922
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.4.0
> Environment: CentOS 6.4
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Attachments: YARN-1922.1.patch, YARN-1922.2.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
