Sangjin Lee created MAPREDUCE-5841:
--------------------------------------
Summary: 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
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.
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
(v6.2#6252)
