Allen Wittenauer commented on YARN-796:

bq. set labels on yarn-site.xml in each NM, and NM will report such labels to RM

This breaks configuration management; changing the yarn-site.xml on a per-node 
basis means ops folks will lose the ability to use system tools to verify the 
file's integrity (e.g., rpm -V).  

bq. If it's not, could you please give me more details about what is "dynamic 
labels generated from an admin on the NM" in your thinking

As I've said before, I basically want something similar to the health check 
code: I provide something executable that the NM can run at runtime that will 
provide the list of labels. If we need to add labels, it's updating the script 
which is a much smaller footprint than redeploying HADOOP_CONF_DIR everywhere.

> 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
>    Affects Versions: 2.4.1
>            Reporter: Arun C Murthy
>            Assignee: Wangda Tan
>         Attachments: LabelBasedScheduling.pdf, 
> Node-labels-Requirements-Design-doc-V1.pdf, 
> Node-labels-Requirements-Design-doc-V2.pdf, YARN-796.node-label.demo.patch.1, 
> YARN-796.patch, YARN-796.patch4
> 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

Reply via email to