[YARN-76] killApplication doesn't fully kill application master on Mac OS

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate

Environment

Failed on MacOS. OK on Linux

• Assignee: Xuan Gong
• Reporter: Bo Wang
• Created: 01/Sep/12 00:11
• Updated: 23/Jan/17 15:29
• Resolved: 08/Jun/15 23:39

Description

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.

Issue Links

• duplicates: YARN-1754 Container process is not really killed
• is duplicated by: YARN-3561 Non-AM Containers continue to run even after AM is stopped
• relates to: APEXCORE-608 Streaming Containers use stale RPC proxy after connection is closed