hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haibo Chen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-6801) Fix flaky TestKill.testKillJob()
Date Wed, 26 Oct 2016 15:54:58 GMT
Haibo Chen created MAPREDUCE-6801:

             Summary: Fix flaky TestKill.testKillJob()
                 Key: MAPREDUCE-6801
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6801
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: mrv2
    Affects Versions: 3.0.0-alpha1
            Reporter: Haibo Chen
            Assignee: Haibo Chen

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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org

View raw message