[
https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114754#comment-13114754
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3054:
----------------------------------------------------
bq. Also jobs which are in the queue and get killed have no record in the
system( ! ) (except for the fleeting cache in RM). I can't think of any
solution other than MAPREDUCE-3061.
One idea just stuck me - we can make the JobClient write out the history-file
for these jobs which are killed when idling in the queue.
> Unable to kill submitted jobs
> -----------------------------
>
> Key: MAPREDUCE-3054
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3054
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Siddharth Seth
> Assignee: Mahadev konar
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-3054.patch, MAPREDUCE-3054.patch,
> MAPREDUCE-3054.patch, MAPREDUCE-3054.patch
>
>
> Found by Philip Su
> The "mapred job -kill" command
> appears to succeed, but listing the jobs again shows that the job supposedly
> killed is still there.
> {code}
> mapred job -list
> Total jobs:2
> JobId State StartTime UserName Queue Priority
> SchedulingInfo
> job_1316203984216_0002 PREP 1316204924937 hadoopqa default NORMAL
> job_1316203984216_0001 PREP 1316204031206 hadoopqa default NORMAL
> mapred job -kill job_1316203984216_0002
> Killed job job_1316203984216_0002
> mapred job -list
> Total jobs:2
> JobId State StartTime UserName Queue Priority
> SchedulingInfo
> job_1316203984216_0002 PREP 1316204924937 hadoopqa default NORMAL
> job_1316203984216_0001 PREP 1316204031206 hadoopqa default NORMAL
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
