Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <28120389.23621291841705482.JavaMail.jira@thor>
Date: Wed, 8 Dec 2010 15:55:05 -0500 (EST)
From: "Dick King (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-2214) TaskTracker should release slot
 if task is not launched
In-Reply-To: <3319138.23521291841341185.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dick King commented on MAPREDUCE-2214:
--------------------------------------

Speculative execution is a legitimate way a task can become {{SUCCEEDED}} while an attempt on that task is waiting to get launched.

> TaskTracker should release slot if task is not launched
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-2214
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2214
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.20.1
>            Reporter: Ramkumar Vadali
>            Assignee: Ramkumar Vadali
>
> TaskTracker.TaskInProgress.launchTask() does not launch a task if it is not in an expected state. However, in the case where the task is not launched, the slot is not released. We have observed this in production - the task was in SUCCEEDED state by the time launchTask() got to it and then the slot was never released. It is not clear how the task got into that state, but it is better to handle the case.

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