You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Devaraj Das (JIRA)" <ji...@apache.org> on 2009/05/08 12:23:45 UTC
[jira] Resolved: (HADOOP-5636) Job is left in Running state after a
killJob
[ 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.