hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5636) Job is left in Running state after a killJob
Date Tue, 07 Apr 2009 11:39:13 GMT

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

Amareshwari Sriramadasu updated HADOOP-5636:
--------------------------------------------

    Summary: Job is left in Running state after a killJob  (was: Job is left i Running state
after a killJob)

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