[
https://issues.apache.org/jira/browse/MAPREDUCE-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600406#comment-13600406
]
Hadoop QA commented on MAPREDUCE-5060:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12573398/MR-5060.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3405//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3405//console
This message is automatically generated.
> 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
> Attachments: 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
