You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Yufei Gu (JIRA)" <ji...@apache.org> on 2017/10/02 23:35:01 UTC
[jira] [Comment Edited] (YARN-2162) add ability in Fair Scheduler
to optionally configure maxResources in terms of percentage
[ https://issues.apache.org/jira/browse/YARN-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189056#comment-16189056 ]
Yufei Gu edited comment on YARN-2162 at 10/2/17 11:34 PM:
----------------------------------------------------------
Run SLS with 400 nodes, 200 apps, and 2k containers. Both base line and patch YARN-2162 runs 20 times. !test-400nm-200app-2k_NODE_UPDATE.timecost.svg|thumbnail!. Please ignore the "Resource Type 0", it is the yarn-2162 patch actually. Don't see obvious performance regression. The patch version even performs a little better due to normal fluctuation.
was (Author: yufeigu):
Run SLS with 400 nodes, 200 apps, and 2k containers. Both base line and patch YARN-2162 runs 20 times. !attachment-name.jpg|thumbnail!. Please ignore the "Resource Type 0", it is the yarn-2162 patch actually. Don't see obvious performance regression. The patch version even performs a little better due to normal fluctuation.
> 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
> Attachments: test-400nm-200app-2k_NODE_UPDATE.timecost.svg, 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
>
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org