[ 
https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219019#comment-14219019
 ] 

Sunil G commented on YARN-1963:
-------------------------------

Thank you [~leftnoteasy]

bq. I'd prefer highest + default priority.
This configuration will make it easier for admins to config the same. Still I 
am not convinced with default acceptance coming from lower priorities by 
default. But I am not seeing any use case where this lower priorities are a 
problem also. Yes, we can have this as highest + default (this one i already 
have). Instead of labels per queue, it will be changed as highest per queue. I 
will update doc as per same, also my patch.

bq. extra complexity both in implementation and configuration
I agree about the more complicated config and implementation for this part. As 
you mentioned, if a preemption feature related to  YARN-2069 runs in parallel, 
then the issue which I pointed out can be solved. So user-limit factor 
preemption if considers priority also, we can get the head room which is 
needed. User has to enable this preemption though. If this is workaround way is 
fine for resolving the issue mentioned, then I will file a jira to relate 
priority with user-limit preemption. Kindly share your thoughts.

bq. I didn't see any related code in YarnClient
Yes, this code is now in YarnRunner which is part of map reduce. I wanted to 
see it with YarnClient.

> 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
>
>
> 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)

Reply via email to