[ https://issues.apache.org/jira/browse/YARN-7645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313888#comment-16313888 ]
Ray Chiang commented on YARN-7645: ---------------------------------- +1. I'm having difficulty reproducing the original error on my setup, but I'm not seeing any test issues with the new patch either. > TestContainerResourceUsage#testUsageAfterAMRestartWithMultipleContainers is > flakey with FairScheduler > ----------------------------------------------------------------------------------------------------- > > Key: YARN-7645 > URL: https://issues.apache.org/jira/browse/YARN-7645 > Project: Hadoop YARN > Issue Type: Bug > Components: test > Affects Versions: 3.0.0 > Reporter: Robert Kanter > Assignee: Robert Kanter > Attachments: YARN-7645.001.patch > > > We've noticed some flakiness in > {{TestContainerResourceUsage#testUsageAfterAMRestartWithMultipleContainers}} > when using {{FairScheduler}}: > {noformat} > java.lang.AssertionError: Attempt state is not correct (timeout). > expected:<ALLOCATED> but was:<SCHEDULED> > at > org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.amRestartTests(TestContainerResourceUsage.java:275) > at > org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageAfterAMRestartWithMultipleContainers(TestContainerResourceUsage.java:254) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org