[
https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365408#comment-14365408
]
Sunil G commented on YARN-1963:
-------------------------------
HI [~vinodkv] , [~leftnoteasy] , [~eepayne] [~jlowe]
Using a priority as integer itself to scheduler's will be the first target, A
manager which can act as a single point of contact which can translate from
label to integer and vice versa. Yes, this will be an added complexity in RM,
but if it can be taken out of Scheduler it reduces much of manipulation logic.
{noformat}
<alias>
0:VERY_LOW, 1:LOW, 2:NORMAL, 3:HIGH, 4:VERY_HIGH
</alias>
{noformat}
I feel we can make such label config in a common place which can be accessible
for any schedulers.
> Support priorities across applications within the same queue
> -------------------------------------------------------------
>
> Key: YARN-1963
> URL: https://issues.apache.org/jira/browse/YARN-1963
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: api, resourcemanager
> Reporter: Arun C Murthy
> Assignee: Sunil G
> Attachments: 0001-YARN-1963-prototype.patch, YARN Application
> Priorities Design.pdf, YARN Application Priorities Design_01.pdf
>
>
> It will be very useful to support priorities among applications within the
> same queue, particularly in production scenarios. It allows for finer-grained
> controls without having to force admins to create a multitude of queues, plus
> allows existing applications to continue using existing queues which are
> usually part of institutional memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
