hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4089) Hung Tasks never time out.
Date Mon, 02 Apr 2012 16:29:25 GMT

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

Robert Joseph Evans commented on MAPREDUCE-4089:
------------------------------------------------

The test failures appear to be caused by either existing issues or Bind errors, just like
before.  All of the failures are in the RM, which has no dependency on the code that was changed
with this patch.
                
> Hung Tasks never time out. 
> ---------------------------
>
>                 Key: MAPREDUCE-4089
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4089
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.2, 2.0.0, trunk
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Blocker
>         Attachments: MR-4089.txt, MR-4089.txt, MR-4089.txt
>
>
> The AM will timeout a task through mapreduce.task.timeout only when it does not hear
from the task within the given timeframe.  On 1.0 a task must be making progress, either by
reading input from HDFS, writing output to HDFS, writing to a log, or calling a special method
to inform it that it is still making progress.
> This is because on 0.23 a status update which happens every 3 seconds is counted as progress.

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

        

Mime
View raw message