[
https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289619#comment-14289619
]
Sunil G commented on YARN-1963:
-------------------------------
As per discussion happened in YARN-2896 with [~eepayne] and [~leftnoteasy],
there is proposal to use Integer alone as priority from client and as well as
in server. As per design doc, a priority label was used as wrapper for user and
internally server was using corresponding integer with same. We can continue
discussion on this here in parent JIRA. Looping [~vinodkv].
Current idea:
{noformat}
yarn.prority-labels = low:2, medium:4, high:6
{noformat}
Proposed:
{noformat}
yarn.application.priority = 2, 3 , 4
{noformat}
Thank you for sharing your thoughts. I will now upload scheduler changes which
can be reviewed meantime.
> 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: 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)
