Mayank Bansal commented on YARN-2069:

Hi [~wangda],

Good point , I missed it.

I have updated the patch accordingly, Please review.

Hi [~sunilg]

Previously as well we dont wait for one more cycle to happen before we start 
preemption. it drops reservation and then count against res to Obtain and 
return rest of the containers to preempt, 
I am following the same pattern.
So essentially I am droping reservation , then try to balance the queue with 
user limits and then get rest of the containers and then send them to preempt.


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

Reply via email to