hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7410) Cleanup FixedValueResource to avoid dependency to ResourceUtils
Date Thu, 02 Nov 2017 17:32:00 GMT

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

Wangda Tan commented on YARN-7410:

Thanks reviews from [~templedf]. [~sunilg] could you help to commit this? 

[~templedf], any concerns of backporting YARN-7307 and this to branch-3.0?

> 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
>            Priority: Major
>         Attachments: YARN-7410.001.patch, YARN-7410.002.patch, YARN-7410.003.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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message