[MAPREDUCE-2667] MR279: mapred job -kill leaves application in RUNNING state

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.23.0
• Component/s: mrv2
• Hadoop Flags: Reviewed
• Assignee: Thomas Graves
• Reporter: Thomas Graves
• Created: 08/Jul/11 21:20
• Updated: 15/Nov/11 00:48
• Resolved: 25/Jul/11 04:30

Description

the mapred job -kill command doesn't seem to fully clean up the application.

If you kill a job and run mapred job -list again it still shows up as running:

mapred job -kill job_1310072430717_0003
Killed job job_1310072430717_0003

mapred job -list
Total jobs:1
JobId State StartTime UserName Queue Priority SchedulingInfo
job_1310072430717_0003 RUNNING 0 tgraves default NORMAL 98.139.92.22:19888/yarn/job/job_1310072430717_3_3

Running kill again will error out.

It also still shows up in the RM Applications UI as running with a note of: Kill Job received from client
job_1310072430717_0003 Job received Kill while in RUNNING state.