[
https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343718#comment-14343718
]
Vinod Kumar Vavilapalli commented on YARN-2069:
-----------------------------------------------
In the above example, there are two choices.
# Respecting app order: {15%, 6%, %6, %6, %6} (total is 39%)
# Respecting user share: {9%, 9%, %9, %6, %6} (total is 39%)
I think without YARN-2113 (which is really about making sure allocation also
actively balances users via preemption), doing (1) above is not going to help -
allocation will come in and imbalance users anyways. So, it's ok to implement
either. If the patch has already gone ahead and implemented (2), I'd vote for
keeping it as is and make a note on YARN-2113 to change it.
> 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-10.patch,
> YARN-2069-trunk-2.patch, YARN-2069-trunk-3.patch, YARN-2069-trunk-4.patch,
> YARN-2069-trunk-5.patch, YARN-2069-trunk-6.patch, YARN-2069-trunk-7.patch,
> YARN-2069-trunk-8.patch, YARN-2069-trunk-9.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.3.4#6332)
