Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 18 Apr 2017 14:45:41 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13021256.1479328337000.306557.1492526741862@Atlassian.JIRA>
In-Reply-To: <JIRA.13021256.1479328337000@Atlassian.JIRA>
References: <JIRA.13021256.1479328337000@Atlassian.JIRA> <JIRA.13021256.1479328337470@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-5892) Capacity Scheduler: Support
 user-specific minimum user limit percent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 18 Apr 2017 14:45:48 -0000


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

Jason Lowe commented on YARN-5892:
----------------------------------

I'm +1 for weight == 0.  As long as it doesn't break the code (e.g.: division by zero, etc.) and does something semantically consistent with weights then I don't see why we should disallow it.  
A practical use of this could be to essentially "pause" a user in a queue -- it won't reject the user's app submissions like changing the queue ACLs would, but the user will get very little to no resources until the weight becomes non-zero.

I'm also +1 for having the weight be less than 1.  It looks like it works with the patch now, and I worry that the longer we keep support for it out of the codebase the more difficult it can become to introduce it later.  People will see in the existing code that it cannot be less than 1 and end up assuming (explicitly or implicitly) that it never will.


> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org