Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.0-alpha1
-
None
-
Reviewed
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
Attachments
Issue Links
- is duplicated by
-
MAPREDUCE-6802 TestKill.testKillJob() fails intermittently on Power
- Resolved
Please check comment on
MAPREDUCE-6802for ppc, tried this on x86 multiple times and it did not fail. But fails around 2 times out of 10 on Power-RHEL machine.