hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5547) Job history should not be flushed to JHS until AM gets unregistered
Date Thu, 27 Feb 2014 23:12:20 GMT

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

Jason Lowe commented on MAPREDUCE-5547:
---------------------------------------

IMHO job status and RM being out of sync is something that can always happen.  This is similar
to Bobby's point about the _SUCCESS file and how killed jobs are handled. In this point of
the job flow, the next AM attempt should not re-commit any output (due to existence of the
committing file).  Is there a real-world use case that having history reporting success but
RM reporting running/failed is going to break something?

> Job history should not be flushed to JHS until AM gets unregistered
> -------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5547
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5547
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>         Attachments: MAPREDUCE-5547.1.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message