[
https://issues.apache.org/jira/browse/YARN-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated YARN-6359:
--------------------------------
Attachment: YARN-6359.001.patch
Despite running it over 1000 times, I wasn't able to reproduce this in my
environment. However, it seems likely that the problem is due to a race
condition between when the metric for the apps killed is checked versus when
that metrics is updated. The 001 patch fixes this by adding some looping code,
with a timeout, similar to what {{MockRM#waitForState}} does. I've verified
that this helps solve the problem by (temporarily) adding in a sleep to the
metrics updating code.
> TestRM#testApplicationKillAtAcceptedState fails rarely due to race condition
> ----------------------------------------------------------------------------
>
> Key: YARN-6359
> URL: https://issues.apache.org/jira/browse/YARN-6359
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
> Affects Versions: 2.9.0, 3.0.0-alpha3
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: YARN-6359.001.patch
>
>
> We've seen (very rarely) a test failure in
> {{TestRM#testApplicationKillAtAcceptedState}}
> {noformat}
> java.lang.AssertionError: expected:<1> but was:<0>
> 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.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.hadoop.yarn.server.resourcemanager.TestRM.testApplicationKillAtAcceptedState(TestRM.java:645)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
