[
https://issues.apache.org/jira/browse/YARN-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wangda Tan updated YARN-7854:
-----------------------------
Comment: was deleted
(was: Thanks [~LambertYe] for investigations. Few general comments.
1. {{yarn_rm_admin/}} is not what we look for namespace. We wanted it to look
like more of like a domain / namespace. Hence {{system.yarn.io/}} kind of name
tag which is what [~leftnoteasy] also was indicating earlier. If you see the
new resource types, we are putting under {{yarn.io/gpu}} or {{yarn.io/fpga}}
etc. So could we have like {{admin.yarn.io}} {{dist.yarn.io}}
{{system.yarn.io}} ? please feel free to suggest ur thoughts.
2. While an app demands a constraint for attributes, they have to specify the
fully qualified name with prefix.
3. If prefix is not given, we can think of looking under centralized namespace
alone.
4. cross validation from RM makes sense as [~Naganarasimha] mentioned.)
> Attach prefixes to different type of node attributes
> ----------------------------------------------------
>
> Key: YARN-7854
> URL: https://issues.apache.org/jira/browse/YARN-7854
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: RM
> Reporter: Weiwei Yang
> Assignee: LiangYe
> Priority: Major
>
> There are multiple types of node attributes depending on which source it
> comes from, includes
> # Centralized: attributes set by users (admin or normal users)
> # Distributed: attributes collected by a certain attribute provider on each
> NM
> # System: some built-in attributes in yarn, set by yarn internal components,
> e.g scheduler
> To better manage these attributes, we introduce the prefix (namespace)
> concept to the an attribute. This Jira is opened to figure out how to attach
> prefixes (automatically/implicitly or explicitly) to different type of
> attributes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
