hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-5746) Errors encountered in MROutputThread after the last map/reduce call can go undetected
Date Thu, 04 Jun 2009 12:47:07 GMT

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

Devaraj Das resolved HADOOP-5746.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.21.0)
                   0.20.1
         Assignee: Amar Kamat
     Hadoop Flags: [Reviewed]

I just committed this. Thanks, Amar!

> 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
>            Assignee: Amar Kamat
>             Fix For: 0.20.1
>
>         Attachments: 5746-reproduce.1.patch, 5746-testcase.patch, 5746.1.patch, 5746.6.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.


Mime
View raw message