You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Siddharth Seth (Updated) (JIRA)" <ji...@apache.org> on 2012/01/09 22:35:42 UTC
[jira] [Updated] (MAPREDUCE-3528) The task timeout check interval
should be configurable independent of mapreduce.task.timeout
[ https://issues.apache.org/jira/browse/MAPREDUCE-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated MAPREDUCE-3528:
--------------------------------------
Attachment: MR3528.txt
Trivial patch - introducing a new config param for the timeout check. Not including a unit test.
> The task timeout check interval should be configurable independent of mapreduce.task.timeout
> --------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3528
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3528
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am, mrv2
> Affects Versions: 0.23.0
> Reporter: Siddharth Seth
> Attachments: MR3528.txt
>
>
> TaskHeartbeatHandler sleeps for 'mapreduce.task.timeout' - between each check. If a task/NM goes bad immediately after starting a task - the timeout is detected in ~2x the configured timeout interval.
--
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