Yuliya Feldman commented on YARN-796:

Agree, what I meant is, we need consider performance of 2 things,
- Time to evaluate a label expression, IMO we need to add labels in per 
container level.
- If it is important to get headroom or how many nodes can be used for an 
expression. The easier expression will be easier for us to get result mentioned 
previously easier.
Regarding time to evaluate label expression - we need to get some performance 
stats on how many ops we can process - I will try to get those performance 
numbers based different levels complexity of expression
Did not do anything to include labels evaluation into calculation of headroom, 
so I don't have comments there

bq. Do you have any ideas about what’s the API will like?
It can be as simple as "yarn rmadmin -loadlabels <local_file_path> 
I am not sure if you mean anything else  

bq. I think for different schedulers, we should specify queue related 
parameters in different configurations. Let’s get more ideas about how to 
specify queue parameters from community before move ahead. 
I have some examples in the document for Fair and Capacity Schedulers

> 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