Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <937655016.1242457005769.JavaMail.jira@brutus>
Date: Fri, 15 May 2009 23:56:45 -0700 (PDT)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5636) Job is left in Running state after
 a killJob
In-Reply-To: <353157256.1239103393413.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-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710081#action_12710081 ] 

Amar Kamat commented on HADOOP-5636:
------------------------------------

@Nigel : Karam tested this patch. 
@Karam : can you please describe how you tested this patch?

> Job is left in Running state after a killJob
> --------------------------------------------
>
>                 Key: HADOOP-5636
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5636
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amar Kamat
>            Priority: Critical
>             Fix For: 0.20.1
>
>         Attachments: HADOOP-5636-v1.0.patch
>
>
> In one scenario, Job was left in Running state forever, when a kill was issued after launching job setup task.

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