[
https://issues.apache.org/jira/browse/MAPREDUCE-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837324#comment-13837324
]
Hadoop QA commented on MAPREDUCE-4901:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12562403/MR-4901-trunk.txt
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4238//console
This message is automatically generated.
> 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.1#6144)
