Naganarasimha G R commented on YARN-2728:

Hi [~wangda],
In the leiu of earlier review 
 in Yarn-2495, 
 Now if user want to leverage change of capacity scheduler, user MUST specify 
1) labels can be accessed by the queue and 2) proportion of resource can be 
accessed by a queue of each label.
Back to the central node label validation discussion, without this, we cannot 
get capacity scheduler work for now. (user cannot specify capacity for a 
unknown node-label for a queue, etc.). 
I feel we can keep the design same and we can have a configuration flag based 
on which we can decide to do the following
# Disable(/throw exception) in CommonNodeLabelsManager.addToCluserNodeLabels & 
removeFromClusterNodeLabels (so that Cluster Node labels are not taken from 
# Support protected method in CommonNodeLabelsManager which updates the label 
mgr with new labels(as cluster node labels) and invoke it from 

By doing this, we will have the flexibility to enable or disable this 
centralized valid cluster node labels functionality in both centralized and 
distributed Node Labels configuration.

> Support for disabling the Centralized NodeLabel validation in Distributed 
> Node Label Configuration setup
> --------------------------------------------------------------------------------------------------------
>                 Key: YARN-2728
>                 URL: https://issues.apache.org/jira/browse/YARN-2728
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
> Currently without Central List of Valid Labels, Capacity scheduler will not 
> be able to work (user cannot specify capacity for a unknown node-label for a 
> queue, etc.). But without disabling the central label validation, Distributed 
> Node Label configuration  feature is not complete. so we need to support this 
> feature

This message was sent by Atlassian JIRA

Reply via email to