Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1665991109.1236339596409.JavaMail.jira@brutus>
Date: Fri, 6 Mar 2009 03:39:56 -0800 (PST)
From: "Vinod K V (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5424) Expired launching tasks affect
 small jobs' execution time
In-Reply-To: <249400507.1236339596202.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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