[
https://issues.apache.org/jira/browse/YARN-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287199#comment-14287199
]
Sunil G commented on YARN-2896:
-------------------------------
Thank you [~eepayne] and [~leftnoteasy] for sharing your thoughts.
It is easier in implementation with integers and directly it can be configured
and operated with. On the other hand Labels makes more readable and easier for
a user to submit an app and visualize same in UI. Same for admins. But as you
mentioned it comes with slighter complexity at RM to be an interface to
scheduler.
This thought of labels was one of initial idea where in design was formulated.
As [~vinodkv] also participated in design, its good to hear his thoughts too.
Also I surely feel that we still need PriorityLabelManager, it can help us in
storing the data from various options such as config files or admin commands or
even REST. Its better to take such complexities out of RMAppManager. Also for
HA cases, PriorityLabelManager itself can help to bring back config loaded from
memory/files. Also scheduler need not have to take any load, and
PrioirtyLabelManager can help in providing priority for app and its acls.
> Server side PB changes for Priority Label Manager and Admin CLI support
> -----------------------------------------------------------------------
>
> Key: YARN-2896
> URL: https://issues.apache.org/jira/browse/YARN-2896
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, resourcemanager
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: 0001-YARN-2896.patch, 0002-YARN-2896.patch,
> 0003-YARN-2896.patch, 0004-YARN-2896.patch
>
>
> Common changes:
> * PB support changes required for Admin APIs
> * PB support for File System store (Priority Label Store)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
