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

MR279: mapred job -kill leaves application in RUNNING state

    Details

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

      Description

      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.

        Attachments

        1. MAPREDUCE-2587-279-v2.patch
          14 kB
          Thomas Graves
        2. MAPREDUCE-2667-mr279.patch
          1 kB
          Thomas Graves
        3. MAPREDUCE-2667-mr279-v2.patch
          1 kB
          Thomas Graves

          Activity

            People

            • Assignee:
              tgraves Thomas Graves
              Reporter:
              tgraves Thomas Graves
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: