[
https://issues.apache.org/jira/browse/YARN-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328582#comment-14328582
]
Sunil G commented on YARN-2693:
-------------------------------
Hi [~leftnoteasy]
Thank you for the update.
NodeLabels and AppPrioirty managers are more or less same, but we cant merge
more closer as we have different PBs for each operation. However a plan can
laid to merge most of FileSystem and Manager classes so that more common part
of code can be shared.
As mentioned, I will move the parsing and config support changes to
RMAppManager (as a separate class), and will have a minimal implementation. I
will still keep this JIRA open so as to handle the same after the major
scheduler changes and api support is done.
> 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
(v6.3.4#6332)
