hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6303) Read timeout when retrying a fetch error can be fatal to a reducer
Date Thu, 02 Apr 2015 19:00:56 GMT

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

Junping Du updated MAPREDUCE-6303:
       Resolution: Fixed
    Fix Version/s: 2.7.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

I have commit this patch to trunk, branch-2 and branch-2.7. Thanks [~jlowe] for contributing
the patch!

> Read timeout when retrying a fetch error can be fatal to a reducer
> ------------------------------------------------------------------
>                 Key: MAPREDUCE-6303
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6303
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Blocker
>             Fix For: 2.7.0
>         Attachments: MAPREDUCE-6303.001.patch
> If a reducer encounters an error trying to fetch from a node then encounters a read timeout
when trying to re-establish the connection then the reducer can fail.  The read timeout exception
can leak to the top of the Fetcher thread which will cause the reduce task to teardown.  This
type of error can repeat across reducer attempts causing jobs to fail due to a single bad

This message was sent by Atlassian JIRA

View raw message