[
https://issues.apache.org/jira/browse/MAPREDUCE-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675099#comment-15675099
]
Haibo Chen commented on MAPREDUCE-6801:
---------------------------------------
Thanks [~varun_saxena] for your reviews and for pointing out another case we
need fix for! I'll incorporate your comments in the new patch shortly.
> 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
> Attachments: mapreduce6801.001.patch
>
>
> TestKill.testKillJob often fails for the same reason with the following error
> message:
> {code}
> 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)
> {code}
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
