Wangda Tan commented on YARN-796:

Really thanks all your comments above,

As Sandy, Alejandro and Allen mentioned, concerns of centralized configuration. 
My thinking is, node label is more dynamic comparing to any other existing 
options of NM.
An important use case we can see is, some customers want to mark label on each 
node indicate which department/team the node belongs to, when a new team comes 
in and new machines added, labels may need to be changed. And also, it is 
possible that the whole cluster is booked to run some huge batch job at 
12am-2am for example. So such labels will be changed frequently. If we only 
have distributed configuration on each node, it is a nightmare for admins to 
I think we should have a same internal interface for destributed/centralized 
configuration. Like what we've done for RMStateStore.

And as Jian Fang mentioned,
bq. doubt about the assumption for admin to configure labels for a cluster.
I think using script to mark labels is a great way to saving configuration 
works. But lots of other use cases need human intervention as well. Good 
examples like from Allen and me.


> 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

Reply via email to