[ https://issues.apache.org/jira/browse/YARN-8944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666749#comment-16666749 ]
Hudson commented on YARN-8944: ------------------------------ SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15332 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/15332/]) YARN-8944. (wwei: rev 1d90a0dd23c5d1bd52d04c303506806d0dc61cd2) * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestContainerAllocation.java > TestContainerAllocation.testUserLimitAllocationMultipleContainers failure > after YARN-8896 > ----------------------------------------------------------------------------------------- > > Key: YARN-8944 > URL: https://issues.apache.org/jira/browse/YARN-8944 > Project: Hadoop YARN > Issue Type: Test > Components: capacity scheduler > Affects Versions: 3.1.2, 3.2.1 > Reporter: Wilfred Spiegelenburg > Assignee: Wilfred Spiegelenburg > Priority: Minor > Fix For: 3.1.2, 3.3.0, 3.2.1 > > Attachments: YARN-8944.001.patch > > > YARN-8896 changes the behaviour of the CapacityScheduler by limiting the > number of containers that can be allocated in one heartbeat. It is an > undocumented change in behaviour. > The change breaks the junit test: > {{TestContainerAllocation.testUserLimitAllocationMultipleContainers}} > The maximum number of containers that gets assigned via the on heartbeat is > 100 and it expects 199 to be assigned. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org