[
https://issues.apache.org/jira/browse/MAPREDUCE-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505636#comment-13505636
]
Robert Joseph Evans commented on MAPREDUCE-4817:
------------------------------------------------
The patch is simple and straight forward I am +1 assuming that Jekins is OK
with it. I am not sure that we need to update the task. The ping is used
check if the task can reach the AM still. If you want to remove it go ahead
and file a JIRA but it may have further ramifications.
> Hardcoded task ping timeout kills tasks localizing large amounts of data
> ------------------------------------------------------------------------
>
> Key: MAPREDUCE-4817
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4817
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster, mr-am
> Affects Versions: 0.23.3, 2.0.3-alpha
> Reporter: Jason Lowe
> Assignee: Thomas Graves
> Priority: Critical
> Attachments: MAPREDUCE-4817.patch, MAPREDUCE-4817.patch
>
>
> When a task is launched and spends more than 5 minutes localizing files, the
> AM will kill the task due to ping timeout. The AM's TaskHeartbeatHandler
> currently tracks tasks via a progress timeout and a ping timeout. The
> progress timeout can be controlled via mapreduce.task.timeout and even
> disabled by setting the property to 0. The ping timeout, however, is
> hardcoded to 5 minutes and cannot be configured. Therefore if the task takes
> too long localizing, it never gets running in order to ping back to the AM
> and the AM kills it due to ping timeout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
