You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Billie Rinaldi (JIRA)" <ji...@apache.org> on 2014/11/01 19:14:34 UTC
[jira] [Updated] (YARN-1922) Process group remains alive after
container process is killed externally
[ 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.4.patch
Updated patch. We're worried about this causing problems for applications like Slider whose containers create a bunch of child processes. It would be great if we could get this fix into 1.6.
> 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, YARN-1922.3.patch, YARN-1922.4.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.3.4#6332)