[
https://issues.apache.org/jira/browse/YARN-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201070#comment-16201070
]
Wangda Tan commented on YARN-7307:
----------------------------------
[~sunilg],
Thanks for working on the patch, several questions/comments:
1) Do you think is it a valid use case which client need to maintain their own
resource-type.xml (different from RM version)?
2) Is there any issue for client load local resource-types.xml, and overwrite
it once receive the resource types info from RM?
To me, answers to 1)/2) are all no. I don't think client should keep a
different version and I don't see any issue if client load resource types first
and overwrite them by responses from RM. So I think we can avoid add the
separate config {{load.resource-types.config-file.for-client}} and already load
{{resource-types.xml}} from classpath.
And should we add resourceTypesInfo to RegisterApplicationMasterResponse? Once
we have that, we can change AMRMClient to automatically update local resource
types after register to RM.
> 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
