You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2011/07/08 23:20:17 UTC

[jira] [Created] (MAPREDUCE-2667) MR279: mapred job -kill leaves application in RUNNING state

MR279: mapred job -kill leaves application in RUNNING state
-----------------------------------------------------------

                 Key: MAPREDUCE-2667
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2667
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: mrv2
            Reporter: Thomas Graves


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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira