Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0-alpha1
    • Fix Version/s: 2.8.0, 3.0.0-alpha2
    • Component/s: mrv2
    • Labels:
      None

      Description

      TestKill.testKillJob often fails for the same reason with the following error message:

      1 tests failed.
      FAILED:  org.apache.hadoop.mapreduce.v2.app.TestKill.testKillJob
      
      Error Message:
      Task state not correct expected:<KILLED> but was:<NEW/SCHEDULED/RUNNING>
      
      Stack Trace:
      java.lang.AssertionError: Task state not correct expected:<KILLED> but was:<NEW/SCHEDULED/RUNNING>
      	at org.junit.Assert.fail(Assert.java:88)
      	at org.junit.Assert.failNotEquals(Assert.java:743)
      	at org.junit.Assert.assertEquals(Assert.java:118)
      	at org.apache.hadoop.mapreduce.v2.app.TestKill.testKillJob(TestKill.java:84)
      

      The root cause is that when the job is in KILLED state from an external view, TaskKillEvents and TaskAttemptKillEvents placed on the event loop queue may not have been processed by the dispatcher thread.

        Attachments

        1. mapreduce6801.001.patch
          1 kB
          Haibo Chen
        2. mapreduce6801.002.patch
          2 kB
          Haibo Chen

          Issue Links

            Activity

              People

              • Assignee:
                haibochen Haibo Chen
                Reporter:
                haibochen Haibo Chen
              • Votes:
                1 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: