hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6409) NM restarts could lead to app failures
Date Mon, 22 Jun 2015 21:04:01 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596634#comment-14596634

Karthik Kambatla commented on MAPREDUCE-6409:

My bad. I misinterpreted Vinod's suggestion to catch only NMNotYetReadyException, don't ask
me how. I somehow thought he was against retries. 

I fully agree with retrying on NMNotYetReadyException alone. 

> 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, MAPREDUCE-6409.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

This message was sent by Atlassian JIRA

View raw message