Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-5841

uber job doesn't terminate on getting mapred job kill

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.0
    • Fix Version/s: 2.4.1
    • Component/s: mrv2
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      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:

      hadoop jar hadoop-mapreduce-client-jobclient-2.3.0-tests.jar sleep -m 1 -r 0 -mt 300000
      

      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.

        Attachments

        1. mapreduce-5841.patch
          11 kB
          Sangjin Lee
        2. mapreduce-5841.patch
          19 kB
          Sangjin Lee

          Activity

            People

            • Assignee:
              sjlee0 Sangjin Lee
              Reporter:
              sjlee0 Sangjin Lee
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: