[
https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682847#comment-13682847
]
Arun C Murthy commented on YARN-796:
------------------------------------
{quote}
Labels are resources which max=1 and a total that is equal to the max number of
containers a node may have (driven by mem or cpu, whichever allows less
containers). Then a node that has a given label-resource always has capability
for it if there is enough capability of memory and/or CPU. Then, a DRF
scheduler could use label-resources for 'fair' allocation decisions.
{quote}
A node can have a large number of admin-specified labels (os, arch, dept etc.
etc.).
Resources have to be well specified and tangible (cpu, memory, disk, network).
We don't want to be recompiling PB defs for adding in unknown number of labels.
Hence, we need to go a separate 'constraint' or 'label' route.
> 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
