[
https://issues.apache.org/jira/browse/YARN-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Payne updated YARN-5892:
-----------------------------
Description:
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}
was:
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}
NOTE: This should be implemented in a way that user-limit-percent-intra-queue
preemption (YARN-2113) should not be affected.
> 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
>
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
