hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5636) Job is left in Running state after a killJob
Date Fri, 08 May 2009 19:56:46 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707499#action_12707499

Hudson commented on HADOOP-5636:

Integrated in Hadoop-trunk #830 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/830/])
    . Prevents a job from going to RUNNING state after it has been  KILLED (this used to happen
when the SetupTask would come back with a success after the job has been killed). Contributed
by Amar Kamat.

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

View raw message