Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1964370097.1241756865884.JavaMail.jira@brutus>
Date: Thu, 7 May 2009 21:27:45 -0700 (PDT)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (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:all-tabpanel ]

Amar Kamat updated HADOOP-5636:
-------------------------------

    Attachment: HADOOP-5636-v1.0.patch

Attaching a patch the fixes this issue by moving a job to running state upon a setup success only if the job is in prep state. Result of test-patch
{code}
[exec] -1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     -1 tests included.  The patch doesn't appear to include any new or modified tests.
     [exec]                         Please justify why no tests are needed for this patch.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec] 
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler warnings.
     [exec] 
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec] 
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
     [exec] 
     [exec]     +1 release audit.  The applied patch does not increase the total number of release audit warnings.
{code}

Running ant test now.

> 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
>            Priority: Critical
>         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.