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

Hudson commented on MAPREDUCE-4817:
-----------------------------------

Integrated in Hadoop-Yarn-trunk #51 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/51/])
    MAPREDUCE-4817. Hardcoded task ping timeout kills tasks localizing large 
amounts of data (tgraves) (Revision 1414873)

     Result = SUCCESS
tgraves : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1414873
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapred/TaskAttemptListenerImpl.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/TaskHeartbeatHandler.java

                
> 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
>             Fix For: 3.0.0, 2.0.3-alpha, 0.23.6
>
>         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

Reply via email to