[YARN-4459] container-executor should only kill process groups

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 2.7.3, 2.6.5, 3.0.0-alpha1
• Component/s: nodemanager
• Hadoop Flags: Reviewed
• Assignee: Jun Gong
• Reporter: Jun Gong
• Created: 15/Dec/15 13:26
• Updated: 14/Oct/19 15:38
• Resolved: 25/May/16 22:08

Description

When calling 'signal_container_as_user' in container-executor, it first checks whether process group exists, if not, it will kill the process itself(if it the process exists). It is not reasonable because that the process group does not exist means corresponding container has finished, if we kill the process itself, we just kill wrong process.

We found it happened in our cluster many times. We used same account for starting NM and submitted app, and container-executor sometimes killed NM(the wrongly killed process might just be a newly started thread and was NM's child process).

Issue Links

• is duplicated by: YARN-3678 DelayedProcessKiller may kill other process other than container
• is related to: YARN-5154 DelayedProcessKiller can kill the wrong process if pid is recycled