[
https://issues.apache.org/jira/browse/HADOOP-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637437#action_12637437
]
Vinod K V commented on HADOOP-4236:
-----------------------------------
bq. This will be fixed in HADOOP-4261
HADOOP-4261 didn't solve this issue, but it did facilitate a work around by
making JobInProgress.terminateJob() package private. So, callers that wish to
kill a job should do something like this:
{code}
if (job.inited()) {
job.kill();
} else {
job.terminateJob(JobStatus.KILLED);
}
{code}
It will be good if we can wrap this into a single useful method for easy use.
> JobTracker.killJob() fails to kill a job if the job is not yet initialized
> --------------------------------------------------------------------------
>
> Key: HADOOP-4236
> URL: https://issues.apache.org/jira/browse/HADOOP-4236
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.0
> Reporter: Amar Kamat
> Assignee: Sharad Agarwal
> Priority: Blocker
> Fix For: 0.19.0
>
>
> HADOOP-3864 made the following changes to {{JobTracker.killJob()}}
> {code}
> public synchronized void killJob(JobID jobid) {
> JobInProgress job = jobs.get(jobid);
> - job.kill();
> + if (job.inited()) {
> + job.kill();
> + }
> }
> {code}
> This is a bug as a job will not get killed if its not yet initialized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
