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

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

Hi Wangda, 

Thank for sharing your comments.

bq. Does this means, any YARN application doesn't need change a line of their 
code,
yarn.app.priority can be passed from client side. And if client can set the 
priority value  to ApplicationSubmissionContext which is received from this 
config, then RM can get the same. All we need a YarnClient implementation for 
taking this config and setting to ApplicationSubmissionContext. ( Something 
similar to queue name which this app is submitted to ).

bq. Specify only highest priority for queue and user
The idea sounds good. The reason for specifying each label needed for a queue 
is because admin can specify the labels applicable for a queue. With high 
priority, we may always end up having default acceptance of lower priorities. 
How do you feel about having this as a range "low-high" 
{noformat}
cluster labels {very_high, high, medium, low}
yarn.scheduler.root.<queue_name>.priority_label=low-high
yarn.scheduler.capacity.root.<queue_name>.high.acl=user1,user2
yarn.scheduler.capacity.root.<queue_name>.low.acl=user3,user4
{noformat}

This was the intention. Please share your thoughts [~vinodkv] [~gp.leftnoteasy] 
 

bq. I think we shouldn't consider user limit within priority level
I have a use case scenario here. There are few applications running in a queue 
from 4 different users (submitted to priority level low) and user-limit factor 
is 20. 5th user has ACL for submitting high priority applications. Because of 
user-limit, he can get only 20% maximum for his high priority apps. This high 
priority apps submitted by user5 may need more resource which intern will be 
rejected by user-limit check. How do you feel this use case?
 
bq. I suggest to add preemption within queue considering priority.
+1. Already filed a subjira for this.

> 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