[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601027#comment-13601027
 ] 

Hudson commented on MAPREDUCE-5060:
-----------------------------------

Integrated in Hadoop-Yarn-trunk #154 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/154/])
    MAPREDUCE-5060. Fetch failures that time out only count against the first 
map task. Contributed by Robert Joseph Evans (Revision 1455740)

     Result = SUCCESS
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1455740
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/Fetcher.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapreduce/task/reduce/TestFetcher.java

                
> 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

Reply via email to