Wangda Tan commented on YARN-3214:

And to your concerns about regression.

YARN-2694 temp restriction of only one node-label per node and per 
resource-request, because there're lots of problems when doing that. We need 
address these problems before let people to use. 2.6 doesn't have multiple node 
label support, so proposal attached in the JIRA isn't a regression.

In general, node label feature is still in alpha stage, after following tasks 
get completed, it can be a much better:
- YARN-2495, distribtued configuration for node label
- YARN-3214,
- YARN-3409, constraints support
- YARN-3362, UI support

Hope this makes sense to you, and looking forward for your thoughts/suggestions.


> Add non-exclusive node labels 
> ------------------------------
>                 Key: YARN-3214
>                 URL: https://issues.apache.org/jira/browse/YARN-3214
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: Non-exclusive-Node-Partition-Design.pdf
> Currently node labels partition the cluster to some sub-clusters so resources 
> cannot be shared between partitioned cluster. 
> With the current implementation of node labels we cannot use the cluster 
> optimally and the throughput of the cluster will suffer.
> We are proposing adding non-exclusive node labels:
> 1. Labeled apps get the preference on Labeled nodes 
> 2. If there is no ask for labeled resources we can assign those nodes to non 
> labeled apps
> 3. If there is any future ask for those resources , we will preempt the non 
> labeled apps and give them back to labeled apps.

This message was sent by Atlassian JIRA

Reply via email to