Details

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

      Description

      Found by Philip Su

      The "mapred job -kill" command
      appears to succeed, but listing the jobs again shows that the job supposedly killed is still there.

      mapred job -list
      Total jobs:2
      JobId   State   StartTime       UserName        Queue   Priority        SchedulingInfo
      job_1316203984216_0002  PREP    1316204924937   hadoopqa        default NORMAL
      job_1316203984216_0001  PREP    1316204031206   hadoopqa        default NORMAL
      
      mapred job -kill job_1316203984216_0002
      Killed job job_1316203984216_0002
      
      mapred job -list
      Total jobs:2
      JobId   State   StartTime       UserName        Queue   Priority        SchedulingInfo
      job_1316203984216_0002  PREP    1316204924937   hadoopqa        default NORMAL
      job_1316203984216_0001  PREP    1316204031206   hadoopqa        default NORMAL
      
      1. MAPREDUCE-3054.patch
        84 kB
        Mahadev konar
      2. MAPREDUCE-3054.patch
        81 kB
        Mahadev konar
      3. MAPREDUCE-3054.patch
        81 kB
        Mahadev konar
      4. MAPREDUCE-3054.patch
        38 kB
        Mahadev konar
      5. MAPREDUCE-3054.patch
        36 kB
        Mahadev konar
      6. MAPREDUCE-3054.patch
        10 kB
        Mahadev konar
      7. MAPREDUCE-3054.patch
        5 kB
        Mahadev konar

        Issue Links

          Activity

            People

            • Assignee:
              Mahadev konar
              Reporter:
              Siddharth Seth
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development