Lohit Vijayarenu commented on YARN-3214:

bq. (P0) A node can belong to at most one partition. All nodes belong to a 
partition unless overridden.

Does this mean one a node we can have only one label? If so, it would become 
too restrictive. Labels on nodes can be seen in multiple dimension (from app's 
resource, machine resource and also usecase resouce, eg backfill jobs are 
placed on specific set of nodes). In those cases we should have ability to have 
multiple labels on node. 

Also, in the documents there is mention of scheduling apps without any labels 
being scheduled on labeled nodes if resources are idle. Does that also cover 
apps which could have different label other than A/B, but still have a label be 
placed on these nodes when there is free resources available?

> 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