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 "Hitesh Shah (JIRA)" <ji...@apache.org> on 2013/02/12 21:59:17 UTC

[jira] [Updated] (MAPREDUCE-4704) TaskHeartbeatHandler misreports a ping timeout as a task timeout

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hitesh Shah updated MAPREDUCE-4704:
-----------------------------------

    Labels: usability  (was: )
    
> TaskHeartbeatHandler misreports a ping timeout as a task timeout
> ----------------------------------------------------------------
>
>                 Key: MAPREDUCE-4704
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4704
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am, mrv2
>    Affects Versions: 0.23.3
>            Reporter: Jason Lowe
>            Priority: Minor
>              Labels: usability
>
> When a task fails to ping within the hardcoded ping timeout of 5 minutes, TaskHeartbeatHandler logs a message reporting the wrong timeout value.  It reports a timeout of mapreduce.task.timeout seconds rather than the 5 minute ping timeout.
> This can lead to user confusion if they try increasing mapreduce.task.timeout and see the log message showing the larger value but the task continues to timeout after only 5 minutes.

--
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