[
https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068017#comment-14068017
]
Sandy Ryza commented on YARN-796:
---------------------------------
I'm worried that the proposal is becoming too complex. Can we try to whittle
the proposal down to a minimum viable feature? I'm not necessarily opposed to
the more advanced parts of it like queue label policies and updating labels on
the fly, and the design should aim to make them possible in the future, but I
don't think they need to be part of the initial implementation.
To me it seems like the essential requirements here are:
* A way for nodes to be tagged with labels
* A way to make scheduling requests based on these labels
I'm also skeptical about the need for adding/removing labels dynamically. Do
we have concrete use cases for this?
Lastly, as BC and Sunil have pointed out, specifying the labels in the
NodeManager confs greatly simplifies configuration when nodes are being added.
Are there advantages to a centralized configuration?
> 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: Sub-task
> Reporter: Arun C Murthy
> Assignee: Wangda Tan
> Attachments: LabelBasedScheduling.pdf,
> Node-labels-Requirements-Design-doc-V1.pdf, YARN-796.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
