hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5841) uber job doesn't terminate on getting mapred job kill
Date Wed, 23 Apr 2014 21:30:16 GMT

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

Jason Lowe commented on MAPREDUCE-5841:

+1 latest patch looks good to me.  Committing this.

> uber job doesn't terminate on getting mapred job kill
> -----------------------------------------------------
>                 Key: MAPREDUCE-5841
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5841
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 2.3.0
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>         Attachments: mapreduce-5841.patch, mapreduce-5841.patch
> If you issue a "mapred job -kill" against a uberized job, the job (and the yarn application)
state transitions to KILLED, but the application master process continues to run. The job
actually runs to completion despite the killed status.
> This can be easily reproduced by running a sleep job:
> {noformat}
> hadoop jar hadoop-mapreduce-client-jobclient-2.3.0-tests.jar sleep -m 1 -r 0 -mt 300000
> {noformat}
> Issue a kill with "mapred job -kill \[job-id\]". The UI will show the job (app) is in
the KILLED state. However, you can see the application master is still running.

This message was sent by Atlassian JIRA

View raw message