[
https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069175#comment-14069175
]
Jian Fang commented on YARN-796:
--------------------------------
* RM has list of valid labels. (hot reloadable)
This requires that RM has a global picture of the cluster before it starts,
which is unlikely to be true in our use case where we provide hadoop as a cloud
platform and the RM does not have any information about the slave nodes until
they join the cluster. Why not just treat all registered lables from NMs as
valid ones? Label validation could be just for resource requests.
* label-expressions support && (AND) only
At least in our use case, OR is often used, not AND
> 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)
