You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Vinod K V (JIRA)" <ji...@apache.org> on 2009/03/06 12:39:56 UTC

[jira] Commented: (HADOOP-5424) Expired launching tasks affect small jobs' execution time

    [ https://issues.apache.org/jira/browse/HADOOP-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679564#action_12679564 ] 

Vinod K V commented on HADOOP-5424:
-----------------------------------

May be we can 'speculatively' launch tasks by tracking the average completion time of tasks' launching. Thoughts?

> Expired launching tasks affect small jobs' execution time
> ---------------------------------------------------------
>
>                 Key: HADOOP-5424
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5424
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Vinod K V
>
> Currently when a task is given to a TT, the JT doesn't mark the task as running till the TT responds back to the JT. And within 10 mins(hard-coded), if the task doesn't come back, then only the task gets relaunched. For small jobs, this is a lot of time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.