[ https://issues.apache.org/jira/browse/YARN-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307772#comment-17307772 ]
Qi Zhu edited comment on YARN-10503 at 3/24/21, 12:06 PM: ---------------------------------------------------------- Thanks [~gandras] for review. I agree with you. After this jira, if we should add a new Jira to change the hard such as ResourceUtils#parseResourcesString, where FPGA and GPU is hardcoded to unified format that ( e.g. memory=4GB,vcores=20,yarn.io/gpu=4 )? cc [~gandras] [~ebadger] [~pbacsko] was (Author: zhuqi): Thanks [~gandras] for review. I agree with you. After this jira, if we can add a new Jira to change the hard such as ResourceUtils#parseResourcesString, where FPGA and GPU is hardcoded. cc [~gandras] [~ebadger] [~pbacsko] > 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 > Reporter: Qi Zhu > Assignee: Qi Zhu > Priority: Critical > Attachments: YARN-10503.001.patch, YARN-10503.002.patch, > YARN-10503.003.patch, YARN-10503.004.patch > > > 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.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org