[ https://issues.apache.org/jira/browse/YARN-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198176#comment-16198176 ]
Yufei Gu commented on YARN-2162: -------------------------------- [~wangda], these will be fixed by YARN-7270. > add ability in Fair Scheduler to optionally configure maxResources in terms > of percentage > ----------------------------------------------------------------------------------------- > > Key: YARN-2162 > URL: https://issues.apache.org/jira/browse/YARN-2162 > Project: Hadoop YARN > Issue Type: Improvement > Components: fairscheduler, scheduler > Reporter: Ashwin Shankar > Assignee: Yufei Gu > Labels: scheduler > Fix For: 2.9.0, 3.0.0, 3.1.0 > > Attachments: YARN-2162.001.patch, YARN-2162.002.patch, > YARN-2162.003.patch, YARN-2162.004.patch, YARN-2162.005.patch, > YARN-2162.006.patch, YARN-2162.007.patch, YARN-2162.008.patch, > YARN-2162.branch-2.010.patch, YARN-2162.branch-3.0.009.patch, > test-400nm-200app-2k_NODE_UPDATE.timecost.svg > > > minResources and maxResources in fair scheduler configs are expressed in > terms of absolute numbers X mb, Y vcores. > As a result, when we expand or shrink our hadoop cluster, we need to > recalculate and change minResources/maxResources accordingly, which is pretty > inconvenient. > We can circumvent this problem if we can optionally configure these > properties in terms of percentage of cluster capacity. -- 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