[
https://issues.apache.org/jira/browse/MAPREDUCE-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524554#comment-14524554
]
Hadoop QA commented on MAPREDUCE-4136:
--------------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {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/12522230/mapreduce-4136.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5493/console |
This message was automatically generated.
> Hadoop streaming might succeed even through reducer fails
> ---------------------------------------------------------
>
> Key: MAPREDUCE-4136
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4136
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/streaming
> Affects Versions: 0.20.205.0
> Reporter: Wouter de Bie
> Attachments: mapreduce-4136.patch
>
>
> Hadoop streaming can even succeed even though the reducer has failed. This
> happens when Hadoop calls {{PipeReducer.close()}}, but in the mean time the
> reducer has failed and the process has died. When {{clientOut_.flush()}}
> throws an {{IOException}} in {{PipeMapRed.mapRedFinish()}} this exception is
> caught but only logged. The exit status of the child process is never checked
> and task is marked as successful.
> I've attached a patch that seems to fix it for us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
