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 "Bo Wang (JIRA)" <ji...@apache.org> on 2012/09/01 02:13:07 UTC
[jira] [Created] (YARN-76) killApplication doesn't fully kill
application master
Bo Wang created YARN-76:
---------------------------
Summary: killApplication doesn't fully kill application master
Key: YARN-76
URL: https://issues.apache.org/jira/browse/YARN-76
Project: Hadoop YARN
Issue Type: Bug
Environment: Failed on MacOS. OK on Linux
Reporter: Bo Wang
When client sends a ClientRMProtocol#killApplication to RM, the corresponding AM is supposed to be killed. However, on Mac OS, the AM is still alive (w/o any interruption).
I figured out part of the reason after some debugging. NM starts a AM with command like "/bin/bash -c /path/to/java SampleAM". This command is executed in a process (say with PID 0001), which starts another Java process (say with PID 0002). When NM kills the AM, it send SIGTERM and then SIGKILL to the bash process (PID 0001). In Linux, the death of the bash process (PID 0001) will trigger the kill of the Java process (PID 0002). However, in Mac OS, only the bash process is killed. The Java process is in the wild since then.
Note: on Mac OS, DefaultContainerExecutor is used rather than LinuxContainerExecutor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-76) killApplication doesn't fully kill
application master
Posted by "Bo Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447902#comment-13447902 ]
Bo Wang commented on YARN-76:
-----------------------------
Vinod, I wonder if you are interested and have time to look at this issue. It's a problem for MacOS, not sure how it works on Windows.
Thanks,
Bo
> killApplication doesn't fully kill application master
> -----------------------------------------------------
>
> Key: YARN-76
> URL: https://issues.apache.org/jira/browse/YARN-76
> Project: Hadoop YARN
> Issue Type: Bug
> Environment: Failed on MacOS. OK on Linux
> Reporter: Bo Wang
>
> When client sends a ClientRMProtocol#killApplication to RM, the corresponding AM is supposed to be killed. However, on Mac OS, the AM is still alive (w/o any interruption).
> I figured out part of the reason after some debugging. NM starts a AM with command like "/bin/bash -c /path/to/java SampleAM". This command is executed in a process (say with PID 0001), which starts another Java process (say with PID 0002). When NM kills the AM, it send SIGTERM and then SIGKILL to the bash process (PID 0001). In Linux, the death of the bash process (PID 0001) will trigger the kill of the Java process (PID 0002). However, in Mac OS, only the bash process is killed. The Java process is in the wild since then.
> Note: on Mac OS, DefaultContainerExecutor is used rather than LinuxContainerExecutor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira