Wangda Tan commented on YARN-2693:

After thinking about this, I feel like maybe this part is not required before 
adding major functionalities. 

I found existing implementation of priority label manager is very similar to 
node label manager, but they're two different use cases.

In node label manager, each node can be assigned labels, there're lots of 
mappings in the cluster. 
However, priority labels will be much simpler, less than 2 dozens of text-based 
priority labels should satisfy most use cases, and priority labels will not 
likely to be changed frequently.

So what I suggest now is making a simple configuration-based labels first, if 
RM HA need to be supported, admin can put same priority-label configuration 
item to different RM nodes : now we don't have a centralized configuration for 
Hadoop daemon, we assume different RM nodes should have same yarn-site.xml 

After major functionality completed (saying RM / scheduler / API / Client 
side), more time could be spent on this part :).


> Priority Label Manager in RM to manage priority labels
> ------------------------------------------------------
>                 Key: YARN-2693
>                 URL: https://issues.apache.org/jira/browse/YARN-2693
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-2693.patch, 0002-YARN-2693.patch, 
> 0003-YARN-2693.patch, 0004-YARN-2693.patch, 0005-YARN-2693.patch
> Focus of this JIRA is to have a centralized service to handle priority labels.
> Support operations such as
> * Add/Delete priority label to a specified queue
> * Manage integer mapping associated with each priority label
> * Support managing default priority label of a given queue
> * ACL support in queue level for priority label
> * Expose interface to RM to validate priority label
> Storage for this labels will be done in FileSystem and in Memory similar to 
> NodeLabel
> * FileSystem Based : persistent across RM restart
> * Memory Based: non-persistent across RM restart

This message was sent by Atlassian JIRA

Reply via email to