[
https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated YARN-10503:
------------------------------
Affects Version/s: 3.3.1
3.4.0
> Support queue capacity in terms of absolute resources with custom
> resourceType.
> -------------------------------------------------------------------------------
>
> Key: YARN-10503
> URL: https://issues.apache.org/jira/browse/YARN-10503
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: gpu
> Affects Versions: 3.4.0, 3.3.1
> Reporter: Qi Zhu
> Assignee: Qi Zhu
> Priority: Critical
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.1, 3.2.4
>
> Attachments: YARN-10503-branch-3.3.010.patch, YARN-10503.001.patch,
> YARN-10503.002.patch, YARN-10503.003.patch, YARN-10503.004.patch,
> YARN-10503.005.patch, YARN-10503.006.patch, YARN-10503.007.patch,
> YARN-10503.008.patch, YARN-10503.009.patch, YARN-10503.010.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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 Jira will handle GPU first.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
