[
https://issues.apache.org/jira/browse/YARN-9326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781720#comment-16781720
]
Wilfred Spiegelenburg commented on YARN-9326:
---------------------------------------------
Thank you for the update [~adam.antal]
I see the same message when building with those options.
For remark 4: it should have been {{maxContainerAllocation}} as you said.
Please update the text for the vcores.
For all the {{max}} settings if the new definition is used all resource types
are given and or set. Old ones will only set memory and cores and leave
unspecified ones set to 0. All including the unspecified ones are checked
recursively up the queue tree. The *root* queue values are set via
yarn.scheduler.maximum* and the resource type config.
I might not have been completely clear in my comment #6. I am missing the fact
that the {{maxResources}} limit is also enforced recursively. A queue will not
be assigned a container if that assignment would put the queue or its parent(s)
over the maximum resources. It is the same for maxima assigned via
{{maxResources}} on static queues and {{maxChildResources}} for dynamic queues.
> Fair Scheduler configuration defaults are not documented in case of min and
> maxResources
> ----------------------------------------------------------------------------------------
>
> Key: YARN-9326
> URL: https://issues.apache.org/jira/browse/YARN-9326
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: docs, documentation, fairscheduler, yarn
> Affects Versions: 3.2.0
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Major
> Attachments: YARN-9326.001.patch, YARN-9326.002.patch,
> YARN-9326.003.patch, YARN-9326.004.patch
>
>
> The FairScheduler's configuration has the following defaults (from the code:
> javadoc):
> {noformat}
> In new style resources, any resource that is not specified will be set to
> missing or 0%, as appropriate. Also, in the new style resources, units are
> not allowed. Units are assumed from the resource manager's settings for the
> resources when the value isn't a percentage. The missing parameter is only
> used in the case of new style resources without percentages. With new style
> resources with percentages, any missing resources will be assumed to be 100%
> because percentages are only used with maximum resource limits.
> {noformat}
> This is not documented in the hadoop yarn site FairScheduler.html. It is
> quite intuitive, but still need to be documented though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
