hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharad Agarwal (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3924) Add a 'Killed' job status
Date Thu, 18 Sep 2008 11:21:46 GMT

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

Sharad Agarwal commented on HADOOP-3924:
----------------------------------------

Since this patch forks the FAILED status into FAILED and KILLED, there may be potential impact
at places where FAILED is currently being used, so doing a grep on JobStatus.FAILED on trunk
reveals some more places which needs to be aware of KILLED status:
FairScheduler.update() 
TestFairScheduler.testNonRunningJobsAreIgnored()

> Add a 'Killed' job status
> -------------------------
>
>                 Key: HADOOP-3924
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3924
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Assignee: Subramaniam Krishnan
>            Priority: Critical
>         Attachments: patch-3924_v1.txt, patch-3924_v2.txt, patch-3924_v3.txt, patch-3924_v4.txt
>
>
> It is not possible, via APIs, to know if a job has been killed, only that has not been
successful.

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