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

Wangda Tan commented on YARN-2069:
----------------------------------

Hi [~sunilg],
I'm not sure what you meant, I found if there're reserved containers existed in 
multiple apps within a queue, all of their reservation could be dropped if it 
is still beyond limit.
{code}
+        Set<RMContainer> containers = preemptFrom(fc, clusterResource,
+            resourcesToClaimBackFromUser, skippedAMContainerlist,
+            skippedAMSize, null);
{code}
resourceToClaimBackFromUser will be different if app comes from different user.

> CS queue level preemption should respect user-limits
> ----------------------------------------------------
>
>                 Key: YARN-2069
>                 URL: https://issues.apache.org/jira/browse/YARN-2069
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Mayank Bansal
>         Attachments: YARN-2069-trunk-1.patch, YARN-2069-trunk-2.patch, 
> YARN-2069-trunk-3.patch, YARN-2069-trunk-4.patch
>
>
> This is different from (even if related to, and likely share code with) 
> YARN-2113.
> YARN-2113 focuses on making sure that even if queue has its guaranteed 
> capacity, it's individual users are treated in-line with their limits 
> irrespective of when they join in.
> This JIRA is about respecting user-limits while preempting containers to 
> balance queue capacities.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to