[
https://issues.apache.org/jira/browse/YARN-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629115#comment-15629115
]
Varun Saxena commented on YARN-5815:
------------------------------------
We are draining dispatcher just before the new assertions but that does not
guarantee that scheduler event is processed as scheduler events go into another
queue. IIUC, sandflee was attempting to solve this in YARN-5375 because
currently there is no mechanism to wait till ensure scheduler event is
processed. This leads to random test failures for several test cases. We can
just wait on an event expected to be sent to RMApp or attempt, which wont be
the case here.
As of now to fix this, we can simply loop over the condition and sleep till a
certain timeout.
> Random failure
> TestApplicationPriority.testOrderOfActivatingThePriorityApplicationOnRMRestart
> ---------------------------------------------------------------------------------------------
>
> Key: YARN-5815
> URL: https://issues.apache.org/jira/browse/YARN-5815
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bibin A Chundatt
> Assignee: Bibin A Chundatt
> Attachments: YARN-5815.0001.patch, YARN-5815.0002.patch
>
>
> {noformat}
> java.lang.AssertionError: expected:<2> 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.scheduler.capacity.TestApplicationPriority.testOrderOfActivatingThePriorityApplicationOnRMRestart(TestApplicationPriority.java:707)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
