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 "Matteo Bertozzi (JIRA)" <ji...@apache.org> on 2012/06/07 21:57:23 UTC
[jira] [Commented] (MAPREDUCE-4136) Hadoop streaming might succeed
even through reducer fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291260#comment-13291260 ]
Matteo Bertozzi commented on MAPREDUCE-4136:
--------------------------------------------
Yes this is fixed with MAPREDUCE-3790, the IOException during clientOut._flush() is now catched.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira