hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-5718) MR AM should tolerate RM restart/failover during commit
Date Thu, 09 Oct 2014 01:00:37 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Karthik Kambatla resolved MAPREDUCE-5718.
          Resolution: Won't Fix
    Target Version/s:   (was: )

With work-preserving RM/NM restart, one can run into this only when the AM dies or the node
running the AM dies. This is no longer a regression when moving from MR1 to MR2. 

Closing this as "Won't Fix" for now. Please re-open if needed. 

> MR AM should tolerate RM restart/failover during commit
> -------------------------------------------------------
>                 Key: MAPREDUCE-5718
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5718
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>    Affects Versions: 2.3.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>              Labels: ha
>         Attachments: mr-5718-0.patch
> While testing RM HA, we ran into this issue where if the RM fails over while an MR AM
is in the middle of a commit, the subsequent AM gets spawned but dies with a diagnostic message
- "We crashed durring a commit". 

This message was sent by Atlassian JIRA

View raw message