[
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
Ok, here's a compromise. We cant change the job api's to add one to force kill
the job for 0.23. So in my patch, the kill command will send a kill to RM if
the job is not running, if RUNNING, it will send a kill to AM and wait for 10
seconds for it to get killed. If it doesnt get killed, it will send a force
kill to RM.
Also, made a couple of other changes:
- added a little more testing
- changed the finishApplication calls to forceKillApplication in RM
- also changed the response/request names to be clear on what they are doing.
Seems reasonable?
> 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, 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
