[
https://issues.apache.org/jira/browse/MAPREDUCE-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated MAPREDUCE-4089:
-------------------------------------------
Attachment: MR-4089.txt
I thought it would be good to leave the ping timeout in just to be sure that if
someone did disable the progress timeout with a 0 we could still detect a task
that has something bad with it, but I can see your point.
I updated the mapred-default.xml to include information about a value of 0.
This is also to maintain compatability with 1.0.
> 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, 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
