[
https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063783#comment-14063783
]
Sunil G commented on YARN-796:
------------------------------
2. Regarding reservations, how about introducing node-label reservations. Ideas
is like, if an application is lacking resource on a node, it can reserve on
that node as well as to node-label. So when a suitable node update comes from
another node in same node-label, can try allocating container in new node by
unreserving from old node.
3. My approach was more like have a centralized configuration, but later after
some time, if want to add a new node to cluster, then it can start with a
hardcoded label in its yarn-site. In your approach, we need to use REStful API
or admin command to bring this node under one label. May be while start up
itself this node can be set under a label. your thoughts?
> 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)
