[
https://issues.apache.org/jira/browse/YARN-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15775254#comment-15775254
]
Karthik Kambatla commented on YARN-6021:
----------------------------------------
In fact, we recommend using a weight of 0 (that translates to a fairshare of 0)
for ad hoc queues.
Note that we fixed a few bugs over the time with weight/fairshare of 0 and
maxAMShare. If you are running into apps not starting or not getting enough
resources, please try a later version.
> When your allocated minShare of all queue`s added up exceed cluster capacity
> you can get some queue for 0 fairshare
> -------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-6021
> URL: https://issues.apache.org/jira/browse/YARN-6021
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Affects Versions: 2.4.0
> Reporter: Feng Yuan
> Assignee: Feng Yuan
> Priority: Critical
>
> In fair-scheduler.xml,If you config the minshare add up exceed parentQueue`s
> fairshare,for root`s childs,fairshare is cluster capacity.
> You will found your R value look like below when compute childs fairshares:
> 1.0
> 0.5
> 0.25
> 0.125
> 0.0625
> 0.03125
> 0.015625
> 0.0078125
> 0.00390625
> I find this is due to:
> double rMax = 1.0;
> while (resourceUsedWithWeightToResourceRatio(rMax, schedulables, type)
> < totalResource) {
> rMax *= 2.0;
> }
> because resourceUsedWithWeightToResourceRatio will add minShare together.
> As i think is really should we bring in minShare when compute fairshare?
> My advice is we just consider weight is enough,and minshare's guarantee
> will get fulfill when assginContainer!
> Hope suggestion!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
