[
https://issues.apache.org/jira/browse/HADOOP-12317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated HADOOP-12317:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Status: Resolved (was: Patch Available)
Thanks for the fix Anubhav. Committed to trunk and branch-2!
> Applications fail on NM restart on some linux distro because NM container
> recovery declares AM container as LOST
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-12317
> URL: https://issues.apache.org/jira/browse/HADOOP-12317
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Anubhav Dhoot
> Assignee: Anubhav Dhoot
> Priority: Critical
> Fix For: 2.8.0
>
> Attachments: YARN-4046.002.patch, YARN-4046.002.patch,
> YARN-4096.001.patch
>
>
> 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.
> {noformat}
> Application application_1439244348718_0001 failed 1 times due to Attempt
> recovered after RM restartAM Container for
> appattempt_1439244348718_0001_000001 exited with exitCode: 154
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
