Nathan Roberts commented on YARN-1963:

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 

Maybe I'm missing something... Isn't it relatively easy to reason about 2<4 and 
therefore 2 is lower priority than 4? Unix/Linux hasn't had labels for 
priorities and it seems to be working pretty well there. Even if I have labels, 
I have to make sure that all queues and clusters define them precisely the same 
way or I wind up just as confused, if not even more. Just my $0.02

> 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