Wangda Tan commented on YARN-796:

Hi guys,
I've just created a shadow umbrella JIRA (YARN-2492) for YARN-796 (because 
YARN-796 is a sub JIRA), and created a bunch of sub tasks under it.
I also updated a diagram for YARN-796 (YARN-796-Diagram.pdf), hopefully it can 
make you have better understanding of the overall structure and flow.

*Summary of sub tasks:*
* User API changes: YARN-2493
* NodeLabelManager implementation: YARN-2494 (Depends on YARN-2493)
* CapacityScheduler side changes: YARN-2496 (Depends on YARN-2494)
* Respect labels when do preemption in CS: YARN-2498 (Depends on YARN-2496)
* Other changes in RM to support labels: YARN-2500
* Changes in AMRMClient to support labels: YARN-2501 (Depends on YARN-2493)
* Changes in Distributed Shell to support labels: YARN-2502 (Depends on 
* WebUI/RMAdmin-CLI/REST-API: YARN-2503, YARN-2504, YARN-2505 (Depends on 
YARN-2494, YARN-2496, YARN-2500)

[~yufeldman], do you agree about the basic proposal? I think API expose to 
users of our proposals are similar but different in implementation.

Please feel free to add your comments. Thanks a lot!

> 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.consolidate.1.patch, 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