[
https://issues.apache.org/jira/browse/YARN-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597534#comment-14597534
]
Hudson commented on YARN-3842:
------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #237 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/237/])
YARN-3842. NMProxy should retry on NMNotYetReadyException. (Robert Kanter via
kasha) (kasha: rev 5ebf2817e58e1be8214dc1916a694a912075aa0a)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/client/ServerProxy.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/TestNMProxy.java
* hadoop-yarn-project/CHANGES.txt
> 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
> Fix For: 2.7.1
>
> 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)
