[
https://issues.apache.org/jira/browse/MAPREDUCE-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182874#comment-13182874
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3528:
----------------------------------------------------
Neither the findBugs warning, nor the test-failure is related to this patch.
Trivial patch replacing the interval configuration. So, no tests.
+1. Pushing this in.
> 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
> Assignee: 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
