[
https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102644#comment-16102644
]
Sunil G commented on YARN-6858:
-------------------------------
Thanks [~asuresh] for your comments.
Couple of points here:
# CommonNodeLabelsManager has already figured out issues such as storage of
labels (hdfs/files etc) and recovery from that (we use mirror files for this).
Hence we could reuse the same which is already a stable part.
# There is a mapping which is needed per host to attributes and its validation
etc. NodeLabelManager has some valid utils written to cover the same.
# Idea is to extend CommonNodeLabelManager to use these common functionalities
as possible and the extend to have independent functions.
# CLI/REST etc could easily work with a manager and operate easily on same. An
exposed apis to internal scheduler could help to access these attributed in
scheduler, node etc.
I think i understood your suggestions to keep these in SchdeulerNode, but I
guess we might have to reinvent some of these points again by moving there.
Thoughts?
cc/[[email protected]], please correct me if i am wrong or missed
some points.
> 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
>
> Similar to CommonNodeLabelsManager we need to have a centralized manager for
> Node Attributes too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
