hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits
Date Wed, 09 Jul 2014 06:30:06 GMT

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

Sunil G commented on YARN-2069:
-------------------------------

Thanks [~mayank_bansal] for the update. I have still a doubt left here. 
1. *resToObtain* is identified per queue.
2. *balanceUserLimitsinQueueForPreemption* has found *userLimitContainers* containers and
updated *resToObtain*
3. Assume *resToObtain* becomes 0 here.
4. No more check will happen with *preemptFrom* logic as resToObtain is 0.
5. *userLimitContainers* is the only set added to final list and send for preemption.

So my doubt here is, assume there are some reserved containers in applications of that queue,
then these container will not be selected for preemption at this round. 
is this intentional?


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

Mime
View raw message