[
https://issues.apache.org/jira/browse/MAPREDUCE-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444368#comment-13444368
]
Hadoop QA commented on MAPREDUCE-4604:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12542967/MAPREDUCE-4604.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2789//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2789//console
This message is automatically generated.
> In mapred-default, mapreduce.map.maxattempts & mapreduce.reduce.maxattempts
> defaults are set to 4 as well as mapreduce.job.maxtaskfailures.per.tracker.
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4604
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4604
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.3, 2.0.0-alpha, trunk
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Priority: Critical
> Attachments: MAPREDUCE-4604.patch
>
>
> This causes the AM to fail the job at the same time as it blacklists a node,
> thus never actually trying another node.
> Marking as critical because we need this in 0.23.3 before it releases.
--
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
