[
https://issues.apache.org/jira/browse/MAPREDUCE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated MAPREDUCE-3054:
-------------------------------------
Attachment: MAPREDUCE-3054.patch
Update patch after merge and adressing comments from Arun.
Addressed 1 and 2.
For 3, currently we use currentAppAttempt for getting diagnostics info from the
AM for setting status on UI, so we cant set it to null.
For the tranistion in RMApp, actually its valid. It is possible that there can
be a race between an App when submitted and killed such that you can get a kill
when its just new.
Also fixed the test failure introduced in MAPREDUCE-3053.
> 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
