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

Wangda Tan commented on YARN-2009:
----------------------------------

Thanks for updating the patch, [~sunilg] and thanks thorough review suggestions 
from [~eepayne]!

For the AM resource usages while doing intra-queue preemption, as of now, we 
don't consider preempt any AM. in another word, these resources are "frozen".

To simply the problem, instead of creating another pool for AM resource, I 
would prefer to deduct them in all calculations.

There're a few of calculations we should look at:
- totalPreemptedResourceAllowed should deduct total AM usages from the queue. 
(ResourceUsage.getAMUsed of queue may not correct since we inc am-used before 
allocating the container, it's better to add all AM resource from running apps.)
- preemtableFromApp should deduct AM usages from each app

I think the solution should work, let me know if I missed anything.

> Priority support for preemption in ProportionalCapacityPreemptionPolicy
> -----------------------------------------------------------------------
>
>                 Key: YARN-2009
>                 URL: https://issues.apache.org/jira/browse/YARN-2009
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Devaraj K
>            Assignee: Sunil G
>         Attachments: YARN-2009.0001.patch, YARN-2009.0002.patch, 
> YARN-2009.0003.patch, YARN-2009.0004.patch, YARN-2009.0005.patch, 
> YARN-2009.0006.patch, YARN-2009.0007.patch, YARN-2009.0008.patch
>
>
> While preempting containers based on the queue ideal assignment, we may need 
> to consider preempting the low priority application containers first.



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