You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Devaraj Das (JIRA)" <ji...@apache.org> on 2009/04/27 20:58:30 UTC

[jira] Updated: (HADOOP-5746) Errors encountered in MROutputThread after the last map/reduce call can go undetected

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

Devaraj Das updated HADOOP-5746:
--------------------------------

    Attachment: 5746.1.patch

Ok here is an early version of the patch (no testcase yet). The patch applies on 0.18 as well.

> Errors encountered in MROutputThread after the last map/reduce call can go undetected
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5746
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5746
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/streaming
>            Reporter: Devaraj Das
>             Fix For: 0.21.0
>
>         Attachments: 5746.1.patch
>
>
> The framework map/reduce bridge methods make a check at the beginning of the respective methods whether _MROutputThread_ encountered an exception while writing keys/values that the streaming process emitted. However, if the exception happens in _MROutputThread_ after the last call to the map/reduce method, the exception goes undetected. An example of such an exception is an exception from the _DFSClient_ that fails to write to a file on the HDFS.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.