hadoop-mapreduce-issues mailing list archives

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

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

Hadoop QA commented on MAPREDUCE-4901:
--------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | patch |   0m  1s | The patch file was not named according to hadoop's
naming conventions. Please see https://wiki.apache.org/hadoop/HowToContribute for instructions.
|
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply the patch during
dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12562403/MR-4901-trunk.txt |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / b9cebfc |
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5702/console |


This message was 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
>              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)

Mime
View raw message