[
https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328640#comment-16328640
]
Weiwei Yang commented on YARN-6858:
-----------------------------------
Hi [~Naganarasimha], [~sunilg]
I am proposing we don't add such a central node attribute manager, instead like
I commented in YARN-7031, can we just use the distributed manner? That is, let
NM maintains node-attributes state (including persistent) and RM simply relies
on the NM HB report. This is because for node attribute case, NM side discovery
is required. So if centralized mode is used, that means we need to honor the
attributes from NM HB, and at the same time we need to manage attributes set by
admins. That makes RM code more complex. I think it is possible to add NM admin
interface to update individual NM node attribute via CLI or REST, and expose
this to RM admin service is also possible. So from end user view, there is no
difference.
Please let me know your thoughts.
Thanks
> Attribute Manager to store and provide the attributes in RM
> -----------------------------------------------------------
>
> Key: YARN-6858
> URL: https://issues.apache.org/jira/browse/YARN-6858
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, capacityscheduler, client
> Reporter: Naganarasimha G R
> Assignee: Naganarasimha G R
> Priority: Major
>
> Similar to CommonNodeLabelsManager we need to have a centralized manager for
> Node Attributes too.
--
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
