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

Sunil G edited comment on YARN-4945 at 9/16/16 6:50 PM:
--------------------------------------------------------

Thanks [~eepayne],

I think the scenario makes sense to me. And as earlier discussed, an ideal 
order of "preemption to help for better resource distribution" can be in follow 
order *InterQueue => FiFoIntraQueue (User-limit => priority) => etc* . So 
within a queue, user-limit will have the first say. And i think it can be 
incorporated to existing design with minimal refactoring.




was (Author: sunilg):
Thanks [~eepayne],

I think the scenario makes sense to me. And as earlier discussed, an ideal 
order of "preemption to help for better resource distribution" can be in follow 
order {{InterQueue => FiFoIntraQueue (User-limit => priority) => etc }} . So 
within a queue, user-limit will have the first say. And i think it can be 
incorporated to existing design with minimal refactoring.



> [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, YARN-2009.v3.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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to