[
https://issues.apache.org/jira/browse/HADOOP-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632161#action_12632161
]
Sharad Agarwal commented on HADOOP-3924:
----------------------------------------
I noticed that there is a contrib class
org.apache.hadoop.eclipse.server.HadoopJob which uses JobStatus. Should we add
Killed status to JobState enum as well, to be consistent ? Also getState() and
update(JobStatus status) needs to be taken care of for the possible impact.
minor: TestJobKillAndFail doesn't need to have reducer defined, as it is never
used. just set the no of reducers to 0. also there is some duplicate code in
runJobFail and runJobKill which becomes the candidate to move to a single
method, something like:
private RunningJob runJob(String jobName, Class<? extends Mapper> mapper)
> 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.
