[
https://issues.apache.org/jira/browse/YARN-7410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wangda Tan updated YARN-7410:
-----------------------------
Description:
After YARN-7307, Client/AM don't need to keep a up-to-dated resource-type.xml
in the classpath. Instead, they can use YarnClient/ApplicationMasterProtocol
APIs to get the resource types from RM and refresh local types.
One biggest issue of this approach is FixedValueResource: Since we initialize
FixedValueResource in static block, and they won't be updated if resource types
refreshed.
So we need to properly update FixedValueResource to make it can get up-to-date
results
was:
Currently FixedValue Resource constants has some dependencies to ResourceUtils.
This jira will help to cleanup this dependencies.
Thanks [~leftnoteasy] for finding the same.
> Cleanup FixedValueResource to avoid dependency to ResourceUtils
> ---------------------------------------------------------------
>
> Key: YARN-7410
> URL: https://issues.apache.org/jira/browse/YARN-7410
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.1.0
> Reporter: Sunil G
> Assignee: Wangda Tan
> Attachments: YARN-7410.001.patch, YARN-7410.002.patch
>
>
> After YARN-7307, Client/AM don't need to keep a up-to-dated resource-type.xml
> in the classpath. Instead, they can use YarnClient/ApplicationMasterProtocol
> APIs to get the resource types from RM and refresh local types.
> One biggest issue of this approach is FixedValueResource: Since we initialize
> FixedValueResource in static block, and they won't be updated if resource
> types refreshed.
> So we need to properly update FixedValueResource to make it can get
> up-to-date results
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
