[
https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682247#comment-13682247
]
Alejandro Abdelnur commented on YARN-796:
-----------------------------------------
bq. Yes, we'll need to add admin api (via rmadmin) to add/remove labels -
obviously we can allow configs for nodes to startup with set of labels which
they report during registration.
Are labels set via the API persisted in the RM? Where?
When a node registers, how labels are synched between the ones it had in its
config and the ones added/removed via the rmadmin.
Given the usecase you are mentioning it seems these labels are rather static
and determined by node characteristics/features. Wouldn't be simpler to start
without an rmadmin API and just get them from the nodes on node registration?
bq. Initially, I'm thinking AND is simplest for multiple labels. Consecutive
requests, as today, override previous requests.
So the labels would not be part of the resource-request key, right?
bq. Use case, as I mentioned, are ability to segregate clusters based on OS,
processor architecture etc. and hence they aren't resource capabilities, rather
they are constraints which is what labels try to model explicitly.
They are expressing capabilities of a node, just capabilities that don't have a
quantity that drains. My suggestion for modeling this labels as a resource
capability, is that you could use them as a dimension in DRF.
> Allow for (admin) labels on nodes and resource-requests
> -------------------------------------------------------
>
> Key: YARN-796
> URL: https://issues.apache.org/jira/browse/YARN-796
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
>
> It will be useful for admins to specify labels for nodes. Examples of labels
> are OS, processor architecture etc.
> We should expose these labels and allow applications to specify labels on
> resource-requests.
> Obviously we need to support admin operations on adding/removing node labels.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
