[
https://issues.apache.org/jira/browse/YARN-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286610#comment-14286610
]
Wangda Tan commented on YARN-2896:
----------------------------------
I have similar feeling, giving a name per priority is not a scalable way, how
to deal with user wants to have 100 different priorities in the cluster? If
names like "priority_0".."priority_100", isn't it more clear to be a single
number? People can easily compare which number is lower. If we choose number
only, we can avoid a lot of complexities for PB changes and also "priority
label manager" implementation.
> 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)
