hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5636) Job is left in Running state after a killJob
Date Sat, 09 May 2009 13:10:45 GMT

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

Amar Kamat commented on HADOOP-5636:

Its not easy to write a test case for this. The situation is something like this :
# jobtracker schedules a setup task for a job
# user issues a job kill and the job is marked for cleanup
# cleanup returns and the job is marked killed
# setup returns at the same time and moves the job to running state

The only hard part is to make the tracker with the setup return at the same time. 

> 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