hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4901) JobHistoryEventHandler errors should be fatal
Date Mon, 11 May 2015 17:23:00 GMT

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

Robert Joseph Evans commented on MAPREDUCE-4901:


I really don't have a lot of time to devote to this right now.  If you are willing to wait
I can try to take a look at upmerging, but it would probably be faster for someone else to
take it if it is important to them. 

> JobHistoryEventHandler errors should be fatal
> ---------------------------------------------
>                 Key: MAPREDUCE-4901
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4901
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0, 2.0.0-alpha
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>              Labels: BB2015-05-TBR
>         Attachments: MR-4901-trunk.txt
> To be able to truly fix issues like MAPREDUCE-4819 and MAPREDUCE-4832, we need a 2 phase
commit where a subsequent AM can be sure that at a specific point in time it knows exactly
if any tasks/jobs are committing.  The job history log is already used for similar functionality
so we would like to reuse this, but we need to be sure that errors while writing out to the
job history log are now fatal.

This message was sent by Atlassian JIRA

View raw message