Xuan Gong resolved YARN-76.
    Resolution: Duplicate

> killApplication doesn't fully kill application master on Mac OS
> ---------------------------------------------------------------
>                 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
>            Assignee: Xuan Gong
> 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 was sent by Atlassian JIRA

Reply via email to