[
https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507332#comment-14507332
]
Lei Guo commented on YARN-1963:
-------------------------------
Agree with [~jlowe], integer is the base of priority, and label should be just
an alias during application submission. If we keep both label and integer in
the system, it could be complicate when administrator changing the label/range
mapping.
It's true that we do not expect the user to assign many different priorities,
but we may enhance scheduler to calculate priority dynamically based on certain
criteria, for example, the pending time or at certain time frame. In this case,
the priority could be any number.
> 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)
