hadoop-common-dev mailing list archives

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

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

Nigel Daley commented on HADOOP-5636:
-------------------------------------

Devaraj, 
{quote}
     [exec]     -1 tests included.  The patch doesn't appear to include any new or modified
tests.
     [exec]                         Please justify why no tests are needed for this patch.
{quote}
Why did you commit this without a test or justification?

> 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