[
https://issues.apache.org/jira/browse/MAPREDUCE-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888649#comment-15888649
]
Haibo Chen commented on MAPREDUCE-6839:
---------------------------------------
Thanks [~pbacsko] for the addiontial information. Can you be more specific
about what will be affected if the directory is not cleaned properly or how?
Off the top of my head, I cannot think of why staging directory problem could
delay task transition from Scheduled to Running state. If the staging directory
is not directly causing testCrashed to fail, I'd like we include the app.stop
fix in a separate patch.
> TestRecovery.testCrashed failed
> -------------------------------
>
> Key: MAPREDUCE-6839
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6839
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Reporter: Gergő Pásztor
> Assignee: Gergő Pásztor
> Attachments: MAPREDUCE-6839_v1.patch, MAPREDUCE-6839_v2.patch,
> MAPREDUCE-6839_v3.patch
>
>
> TestRecovery#testCrashed is a flaky test.
> Error Message:
> Reduce Task state not correct expected:<RUNNING> but was:<SCHEDULED>
> Stack Trace:
> java.lang.AssertionError: Reduce Task state not correct expected:<RUNNING>
> but was:<SCHEDULED>
> 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.TestRecovery.testCrashed(TestRecovery.java:164)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
