[ https://issues.apache.org/jira/browse/MAPREDUCE-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244282#comment-13244282 ]
Hadoop QA commented on MAPREDUCE-4089: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12520981/MR-4089.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +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 failed these unit tests: org.apache.hadoop.yarn.server.resourcemanager.TestClientRMService org.apache.hadoop.yarn.server.resourcemanager.resourcetracker.TestNMExpiry org.apache.hadoop.yarn.server.resourcemanager.TestAMAuthorization org.apache.hadoop.yarn.server.resourcemanager.TestApplicationACLs +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2125//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2125//console This message is automatically generated. > Hung Tasks never time out. > --------------------------- > > Key: MAPREDUCE-4089 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4089 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.23.2, 2.0.0, trunk > Reporter: Robert Joseph Evans > Assignee: Robert Joseph Evans > Priority: Blocker > Attachments: MR-4089.txt, MR-4089.txt, MR-4089.txt > > > The AM will timeout a task through mapreduce.task.timeout only when it does > not hear from the task within the given timeframe. On 1.0 a task must be > making progress, either by reading input from HDFS, writing output to HDFS, > writing to a log, or calling a special method to inform it that it is still > making progress. > This is because on 0.23 a status update which happens every 3 seconds is > counted as progress. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira