[
https://issues.apache.org/jira/browse/MAPREDUCE-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595079#comment-14595079
]
Karthik Kambatla commented on MAPREDUCE-6409:
---------------------------------------------
How about we remove NMNotYetReadyException in trunk and branch-2 to minimize
any risk, and do MR-only changes for 2.7.1? Filed YARN-3839 to handle that.
[~rkanter] - thanks for picking this up. The patch looks mostly good to me. One
nit: what do you think of suffixing the event-type {{FAILED_BY_YARN}} instead
of {{FAILED_DUE_TO_YARN}}?
Also, what do you think of catching {{YarnException}} instead of
{{NMNotYetReadyException}}? If there is an exception that shouldn't be caught,
it shouldn't be a YarnException? We can fix this as part of YARN-3839. /cc
[~vinodkv], [~jlowe], [~jianhe]
> NM restarts could lead to app failures
> --------------------------------------
>
> Key: MAPREDUCE-6409
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6409
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Karthik Kambatla
> Assignee: Robert Kanter
> Priority: Critical
> Attachments: MAPREDUCE-6409.001.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)
