[ https://issues.apache.org/jira/browse/YARN-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990202#comment-16990202 ]
Eric Payne commented on YARN-10009: ----------------------------------- [~leftnoteasy], thanks for looking at this. bq. is the failure related? I pulled trunk and TestFairSchedulerPreemption ran successfully with and without my patch, so I don't think so. I also put up patch version 003 for branch-2.10 > In Capacity Scheduler, DRC can treat minimum user limit percent as a max when > custom resource is defined > -------------------------------------------------------------------------------------------------------- > > Key: YARN-10009 > URL: https://issues.apache.org/jira/browse/YARN-10009 > Project: Hadoop YARN > Issue Type: Improvement > Components: capacity scheduler > Affects Versions: 2.10.0, 3.3.0, 3.2.1, 3.1.3, 2.11.0 > Reporter: Eric Payne > Assignee: Eric Payne > Priority: Critical > Attachments: YARN-10009.001.patch, YARN-10009.002.patch, > YARN-10009.003.patch, YARN-10009.UT.patch, YARN-10009.branch-2.10.003.patch > > > | |Memory|Vcores|res_1| > |Queue1 Totals|20GB|100|80| > |Resources requested by App1 in Queue1|8GB (40% of total)|8 (8% of total)|80 > (100% of total)| > In the previous use case: > - Queue1 has a value of 25 for {{miminum-user-limit-percent}} > - User1 has requested 8 containers with {{<memory:1GB, vcores:8, res_1:10>}} > each > - {{res_1}} will be the dominant resource this case. > All 8 containers should be assigned by the capacity scheduler, but with min > user limit pct set to 25, only 2 containers are assigned. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org