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 "Qi Zhu (Jira)" <ji...@apache.org> on 2021/03/26 15:55:00 UTC
[jira] [Assigned] (YARN-10171) Add support for increment-allocation
of custom resource types
[ https://issues.apache.org/jira/browse/YARN-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Qi Zhu reassigned YARN-10171:
-----------------------------
Assignee: Qi Zhu
> Add support for increment-allocation of custom resource types
> -------------------------------------------------------------
>
> Key: YARN-10171
> URL: https://issues.apache.org/jira/browse/YARN-10171
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Affects Versions: 3.3.0
> Reporter: Adam Antal
> Assignee: Qi Zhu
> Priority: Minor
>
> The FairScheduler's {{yarn.resource-types.memory-mb.increment-allocation}} and {{yarn.resource-types.vcores.increment-allocation}} configs are converted to the {{yarn.scheduler.minimum-allocation-*}} configs, which is fine for the vcores and memory.
> In case of custom resource types like GPU if {{yarn.resource-types.gpu.increment-allocation}} is set, then CS will not be aware of that. We don't have a {{yarn.scheduler.minimum-allocation-gpu}} setting for this purpose, but {{yarn.resource-types.gpu.min-allocation}} is respected by the {{ResourceCalculator}} through the {{ResourceUtils#getResourceInformationMapFromConfig}} which would provide us with the same behaviour.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org