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

Rushabh S Shah updated MAPREDUCE-4901:
--------------------------------------

    Target Version/s: 3.0.0  (was: 3.0.0, 0.23.11)

Talked to [~revans2] offline and removing 0.23.11 from target version.

> 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
>         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.2#6252)

Reply via email to