hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3528) The task timeout check interval should be configurable independent of mapreduce.task.timeout
Date Mon, 09 Jan 2012 21:35:42 GMT

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

Siddharth Seth updated MAPREDUCE-3528:
--------------------------------------

    Assignee: Siddharth Seth
      Status: Patch Available  (was: Open)
    
> The task timeout check interval should be configurable independent of mapreduce.task.timeout
> --------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3528
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3528
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am, mrv2
>    Affects Versions: 0.23.0
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: MR3528.txt
>
>
> TaskHeartbeatHandler sleeps for 'mapreduce.task.timeout' - between each check. If a task/NM
goes bad immediately after starting a task - the timeout is detected in ~2x the configured
timeout interval.

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