Vinod Kumar Vavilapalli commented on YARN-1963:

As per discussion happened in YARN-2896 with Eric Payne and Wangda Tan, 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 Vinod Kumar Vavilapalli.
Current idea:
yarn.prority-labels = low:2, medium:4, high:6
yarn.application.priority = 2, 3 , 4
Without some sort of labels, it will be very hard for users to reason about the 
definition and relative importance of priorities across queues and cluster. We 
must support the notion of priority-labels to make this feature usable in 

> 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

Reply via email to