hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5060) Fetch failures that time out only count against the first map task
Date Tue, 12 Mar 2013 23:01:13 GMT

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

Jason Lowe updated MAPREDUCE-5060:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.5-beta
                   0.23.7
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks, Bobby.  I committed this to trunk, branch-2, and branch-0.23.
                
> Fetch failures that time out only count against the first map task
> ------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5060
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5060
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Critical
>             Fix For: 0.23.7, 2.0.5-beta
>
>         Attachments: MR-5060-trunk.txt, MR-5060.txt, MR-5060.txt
>
>
> When a fetch failure happens, if the socket has already "connected" it is only counted
against the first map task.  But most of the time it is because of an issue with the Node
itself, not the individual map task, and as such all failures when trying to initiate the
connection should count against all of the tasks.
> This caused a particularly unfortunate job to take an hour an a half longer then it needed
to.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message