[
https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342641#comment-17342641
]
Peter Bacsko edited comment on YARN-10505 at 5/11/21, 3:14 PM:
---------------------------------------------------------------
I would change the naming a bit.
"Relative Percentage" -> "Parent Percentage"
"Absolute Percentage" -> "Cluster Percentage"
I think it's much clearer. Absolute/relative in this context is hard to grasp
or even sounds like an oxymoron.
was (Author: pbacsko):
I would change the naming a bit.
"Relative Percentage" -> "Parent Percentage"
"Absolute Percentage" -> "Cluster Percentage"
I think it's much clearer. Absolute/relative in this context it's hard to grasp
or even sounds like an oxymoron.
> Extend the maximum-capacity property to support Fair Scheduler migration
> ------------------------------------------------------------------------
>
> Key: YARN-10505
> URL: https://issues.apache.org/jira/browse/YARN-10505
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Benjamin Teke
> Priority: Major
>
> The property root.users.maximum-capacity could mean the following things:
> * Relative Percentage: maximum capacity relative to its parent. If it’s set
> to 50, then it means that the capacity is capped with respect to the parent.
> * Absolute Percentage: maximum capacity expressed as a percentage of the
> overall cluster capacity.
>
> Note that Fair Scheduler supports the following settings:
> * Single percentage (absolute)
> * Two percentages (absolute)
> * Absolute resources
>
> It is recommended that all three formats are supported for maximum-capacity
> after introducing weight mode.
--
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
