[HADOOP-12317] Applications fail on NM restart on some linux distro because NM container recovery declares AM container as LOST

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Hadoop Flags: Reviewed
• Assignee: Anubhav Dhoot
• Reporter: Anubhav Dhoot
• Created: 11/Aug/15 18:41
• Updated: 30/Aug/16 01:24
• Resolved: 20/Aug/15 02:02

Description

On a debian machine we have seen node manager recovery of containers fail because the signal syntax for process group may not work. We see errors in checking if process is alive during container recovery which causes the container to be declared as LOST (154) on a NodeManager restart.

The application will fail with error. The attempts are not retried.

Application application_1439244348718_0001 failed 1 times due to Attempt recovered after RM restartAM Container for appattempt_1439244348718_0001_000001 exited with exitCode: 154

Issue Links

• breaks: HADOOP-12441 Fix kill command behavior under some Linux distributions.
• breaks: YARN-3561 Non-AM Containers continue to run even after AM is stopped
• duplicates: YARN-3561 Non-AM Containers continue to run even after AM is stopped
• supercedes: HADOOP-11989 Kill command for process group id throws ExitCodeException