[ https://issues.apache.org/jira/browse/MAPREDUCE-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244572#comment-13244572 ]
Hudson commented on MAPREDUCE-4089: ----------------------------------- Integrated in Hadoop-Common-trunk-Commit #1972 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1972/]) MAPREDUCE-4089. Hung Tasks never time out. (Robert Evans via tgraves) (Revision 1308531) Result = SUCCESS tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1308531 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapred/TaskAttemptListenerImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/TaskHeartbeatHandler.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestTaskHeartbeatHandler.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml > 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 > Fix For: 0.23.3 > > Attachments: MR-4089.txt, MR-4089.txt, 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