You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/05/06 05:26:14 UTC

[jira] [Updated] (MAPREDUCE-4901) JobHistoryEventHandler errors should be fatal

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

Allen Wittenauer updated MAPREDUCE-4901:
----------------------------------------
    Labels: BB2015-05-TBR  (was: )

> 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
(v6.3.4#6332)