[ https://issues.apache.org/jira/browse/YARN-8858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644322#comment-16644322 ]
Weiwei Yang edited comment on YARN-8858 at 10/10/18 1:31 AM: ------------------------------------------------------------- +1. The UT failure should not be related. I applied the patch and tested locally, they work fine. I will commit this shortly. BTW, the checksytle issues were caused by some unused imports in the test class, I will remove them during the commit. was (Author: cheersyang): +1. The UT failure should not be related. I applied the patch and tested locally, they work fine. I will commit this shortly. > CapacityScheduler should respect maximum node resource when per-queue > maximum-allocation is being used. > ------------------------------------------------------------------------------------------------------- > > Key: YARN-8858 > URL: https://issues.apache.org/jira/browse/YARN-8858 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Sumana Sathish > Assignee: Wangda Tan > Priority: Critical > Attachments: YARN-8858.001.patch, YARN-8858.002.patch > > > This issue happens after YARN-8720. > Before that, AMS uses scheduler.getMaximumAllocation to do the normalization. > After that, AMS uses LeafQueue.getMaximumAllocation. The scheduler one uses > nodeTracker.getMaximumAllocation, but the LeafQueue.getMaximum doesn't. > We should use the scheduler.getMaximumAllocation to cap the per-queue's > maximum-allocation every time. -- 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