You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2015/06/23 02:44:02 UTC
[jira] [Updated] (YARN-3842) NMProxy should retry on
NMNotYetReadyException
[ https://issues.apache.org/jira/browse/YARN-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthik Kambatla updated YARN-3842:
-----------------------------------
Summary: NMProxy should retry on NMNotYetReadyException (was: NM restarts could lead to app failures)
> NMProxy should retry on NMNotYetReadyException
> ----------------------------------------------
>
> Key: YARN-3842
> URL: https://issues.apache.org/jira/browse/YARN-3842
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Karthik Kambatla
> Assignee: Robert Kanter
> Priority: Critical
> Attachments: MAPREDUCE-6409.001.patch, MAPREDUCE-6409.002.patch, YARN-3842.001.patch, YARN-3842.002.patch
>
>
> Consider the following scenario:
> 1. RM assigns a container on node N to an app A.
> 2. Node N is restarted
> 3. A tries to launch container on node N.
> 3 could lead to an NMNotYetReadyException depending on whether NM N has registered with the RM. In MR, this is considered a task attempt failure. A few of these could lead to a task/job failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)