hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4817) Hardcoded task ping timeout kills tasks localizing large amounts of data
Date Tue, 27 Nov 2012 03:05:58 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504333#comment-13504333

Vinod Kumar Vavilapalli commented on MAPREDUCE-4817:

I was going to +1 for the proposal, but wasn't comfortable, so dig into some history. Please
see my comments at MAPREDUCE-4089. Like I proposed there, we should knock off the ping thread

But the problem persists, in that, for large enough local-resources, the taskTimeOut may eventually
happen instead which we'll need to address. So, shall we just knock off the ping thread here
and let MAPREDUCE-4818 put in the real fix?
> 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
> 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

View raw message