[ 
https://issues.apache.org/jira/browse/YARN-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198126#comment-16198126
 ] 

Wangda Tan commented on YARN-7307:
----------------------------------

[~andrew.wang], since the whole feature isn't backported to 3.0 yet, I would 
keep it blocking 3.1.0 release for now. Once this is committed, we can consider 
to backport the whole feature to 3.0

> 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
>
> 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

Reply via email to