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 "Eric Payne (Jira)" <ji...@apache.org> on 2020/11/30 22:03:00 UTC
[jira] [Updated] (YARN-10503) Support queue capacity in terms of
absolute resources with more resourceTypes.
[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne updated YARN-10503:
------------------------------
Fix Version/s: (was: 3.4.1)
(was: 3.3.1)
Target Version/s: 3.3.1, 3.4.1
[~zhuqi], please use the "Target Version" field for the desired fix version. The "Fix Version" field is used after the ticket is resolved to indicate which releases have the fix.
> Support queue capacity in terms of absolute resources with more resourceTypes.
> ------------------------------------------------------------------------------
>
> Key: YARN-10503
> URL: https://issues.apache.org/jira/browse/YARN-10503
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: zhuqi
> Assignee: zhuqi
> Priority: Major
>
> Now the absolute resources are memory and cores.
> {code:java}
> /**
> * Different resource types supported.
> */
> public enum AbsoluteResourceType {
> MEMORY, VCORES;
> }{code}
> But in our GPU production clusters, we need to support more resourceTypes.
> It's very import for cluster scaling when with different resourceType absolute demands.
>
--
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