hadoop-common-dev mailing list archives

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

     [ https://issues.apache.org/jira/browse/HADOOP-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Devaraj Das resolved HADOOP-5636.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.20.1
         Assignee: Amar Kamat
     Hadoop Flags: [Reviewed]

I just committed this. Thanks, Amar!

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


Mime
View raw message