[
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 [~sunilg] [~cheersyang] for comments.
# Agree, use DNS format is more appropriate.
# Advocate to Specify the fully qualified name.
# If prefix is not given, default namespace can be configured by
configuration? Because different organizations have different requirements.
# If cross validation is between different sources and they are in different
namespaces, it's not make sense. If from the same source as [~cheersyang]
mentioned, nm collectors or admin or system should handle this situation and
make them the same type or definiteness.)
> 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
