[ 
https://issues.apache.org/jira/browse/MAPREDUCE-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063329#comment-13063329
 ] 

Hadoop QA commented on MAPREDUCE-2667:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12486054/MAPREDUCE-2667-mr279-v2.patch
  against trunk revision 1144403.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/452//console

This message is automatically generated.

> 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
>            Assignee: Thomas Graves
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2587-279-v2.patch, 
> MAPREDUCE-2667-mr279-v2.patch, MAPREDUCE-2667-mr279.patch
>
>
> 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

        

Reply via email to