[ https://issues.apache.org/jira/browse/YARN-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201076#comment-16201076 ]
Wangda Tan commented on YARN-7307: ---------------------------------- Also, instead of adding new dynamic resources fields to ResourceUtils, can we leverage {{initializeResourcesFromResourceInformationMap}} and directly update local types information after {{List<ResourceTypeInfo>}} received from RM? If you do think we should client to opt-out loading resource-types.xml, instead of adding new option to yarn-site.xml, we can add a API to ResourceUtils to opt-in load resource-types.xml (by default it won't load), and we can update ResourceManager/NodeManager to opt-in only. > Revisit resource-types.xml loading behaviors > -------------------------------------------- > > Key: YARN-7307 > URL: https://issues.apache.org/jira/browse/YARN-7307 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager > Reporter: Wangda Tan > Assignee: Sunil G > Priority: Blocker > Attachments: YARN-7307.001.patch > > > Existing feature requires every client has a resource-types.xml in order to > use multiple resource types, should we allow client/AM update supported > resource types via Yarn APIs? -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org