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

Eric Payne edited comment on YARN-5892 at 4/12/17 11:10 PM:
------------------------------------------------------------

By the way, the latest patch reverts the behavior of what is displayed in the 
{{Max Resource}} column in the Capacity Scheduler GUI to the previous behavior. 
The last active value is stored and displayed rather than being recalculated 
based on current active users and resources.

- YARN-5892.008.patch (odd behavior) (User 2 is active):
||*User Name*||*Max Resource*||*Weight*||*Used Resource*||
|{panel:bgColor=yellow}User2{panel}|{panel:bgColor=yellow}<memory:7168, 
vCores:1>{panel}|{panel:bgColor=yellow}0.2{panel}|{panel:bgColor=yellow}<memory:7168,
 vCores:14>{panel}|
|User5|<memory:35840, vCores:1>|1.0|<memory:2560, vCores:5>|

- YARN-5892.009.patch (sane behavior) (user2 is active):
||*User Name*||*Max Resource*||*Weight*||*Used Resource*||
|{panel:bgColor=yellow}User2{panel}|{panel:bgColor=yellow}<memory:7168, 
vCores:1>{panel}|{panel:bgColor=yellow}0.2{panel}|{panel:bgColor=yellow}<memory:7168,
 vCores:14>{panel}|
|User5|<memory:7168, vCores:1>|1.0|<memory:2560, vCores:5>|



was (Author: eepayne):
By the way, the latest patch reverts the behavior of what is displayed in the 
{{Max Resource}} column in the Capacity Scheduler GUI to the previous behavior. 
The last active value is stored and displayed rather than being recalculated 
based on current active users and resources.

- YARN-5892.008.patch (odd behavior) (User 2 is active):
||*User Name*||*Max Resource*||*Weight*||*Used Resource*||
|{panel:bgColor=yellow}User2{panel}|{panel:bgColor=yellow}<memory:7168, 
vCores:1>{panel}|{panel:bgColor=yellow}0.2{panel}|{panel:bgColor=yellow}<memory:7168,
 vCores:14>{panel}|
|User5|<memory:35840, vCores:1>|1.0|<memory:2560, vCores:5>|

- YARN-5892.008.patch (sane behavior) (user2 is active):
||*User Name*||*Max Resource*||*Weight*||*Used Resource*||
|{panel:bgColor=yellow}User2{panel}|{panel:bgColor=yellow}<memory:7168, 
vCores:1>{panel}|{panel:bgColor=yellow}0.2{panel}|{panel:bgColor=yellow}<memory:7168,
 vCores:14>{panel}|
|User5|<memory:7168, vCores:1>|1.0|<memory:2560, vCores:5>|


> Capacity Scheduler: Support user-specific minimum user limit percent
> --------------------------------------------------------------------
>
>                 Key: YARN-5892
>                 URL: https://issues.apache.org/jira/browse/YARN-5892
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>         Attachments: Active users highlighted.jpg, YARN-5892.001.patch, 
> YARN-5892.002.patch, YARN-5892.003.patch, YARN-5892.004.patch, 
> YARN-5892.005.patch, YARN-5892.006.patch, YARN-5892.007.patch, 
> YARN-5892.008.patch, YARN-5892.009.patch
>
>
> Currently, in the capacity scheduler, the {{minimum-user-limit-percent}} 
> property is per queue. A cluster admin should be able to set the minimum user 
> limit percent on a per-user basis within the queue.
> This functionality is needed so that when intra-queue preemption is enabled 
> (YARN-4945 / YARN-2113), some users can be deemed as more important than 
> other users, and resources from VIP users won't be as likely to be preempted.
> For example, if the {{getstuffdone}} queue has a MULP of 25 percent, but user 
> {{jane}} is a power user of queue {{getstuffdone}} and needs to be guaranteed 
> 75 percent, the properties for {{getstuffdone}} and {{jane}} would look like 
> this:
> {code}
>   <property>
>     
> <name>yarn.scheduler.capacity.root.getstuffdone.minimum-user-limit-percent</name>
>     <value>25</value>
>   </property>
>   <property>
>     
> <name>yarn.scheduler.capacity.root.getstuffdone.jane.minimum-user-limit-percent</name>
>     <value>75</value>
>   </property>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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