hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3924) Add a 'Killed' job status
Date Thu, 18 Sep 2008 22:48:44 GMT

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

Arun C Murthy updated HADOOP-3924:

    Status: Open  (was: Patch Available)

Some comments:

1. As Sharad pointed out, this still has to fix the FairScheduler.
2. If possible, can you please make a JobStatus.State enum? Currently we have a bunch of 'private
static final int's.
3. JobInProgress.terminateJob should take the actual state rather than a 'boolean' i.e. KILLED/FAILED.
4. We should *not* introduce a _public_ API in JobInProgress to 'fail' the job. The only one
necessary is the one to 'kill' it. JobInProgress.failJob should be package private.

> 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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message