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

Wangda Tan commented on YARN-4945:
----------------------------------

[~eepayne], 

bq. I need to understand what it would mean to combine all intra-queue priority 
policies into one.
To clarify, we may not combine *all* intra-queue policies into one, but if you 
look at queue internal policies. There are majorly two groups:
1) Fair + user-limit + priority
2) Fifo + user-limit + priority

User-limit and priority will be always on and ordering policy like Fair/Fifo is 
a changeable config. So it makes sense to me to have two different policies, 
one for Fifo (plus priority/UL) and Fair (same plus priority/UL)

bq. If they are combined, then is it still necessary to make 
IntraQueuePreemptionPolicy an interface?
As I mentioned above, we can have a fair intra-queue policy.

To be honest, I haven't thought a good way that a list of policies can better 
solve the priority + user-limit preemption problem. Could you share some ideas 
about it. For example, how to better consider both in the final decision

> [Umbrella] Capacity Scheduler Preemption Within a queue
> -------------------------------------------------------
>
>                 Key: YARN-4945
>                 URL: https://issues.apache.org/jira/browse/YARN-4945
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Wangda Tan
>         Attachments: Intra-Queue Preemption Use Cases.pdf, 
> IntraQueuepreemption-CapacityScheduler (Design).pdf, YARN-2009-wip.2.patch, 
> YARN-2009-wip.patch, YARN-2009-wip.v3.patch, YARN-2009.v0.patch, 
> YARN-2009.v1.patch, YARN-2009.v2.patch
>
>
> This is umbrella ticket to track efforts of preemption within a queue to 
> support features like:
> YARN-2009. YARN-2113. YARN-4781.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to