Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 1 Aug 2017 00:32:00 +0000 (UTC)
From: "Yufei Gu (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12721318.1402858766000.57428.1501547520408@Atlassian.JIRA>
In-Reply-To: <JIRA.12721318.1402858766000@Atlassian.JIRA>
References: <JIRA.12721318.1402858766000@Atlassian.JIRA> <JIRA.12721318.1402858766413@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (YARN-2162) Fair Scheduler :ability to
 optionally configure minResources and maxResources in terms of percentage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 01 Aug 2017 00:32:06 -0000


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

Yufei Gu edited comment on YARN-2162 at 8/1/17 12:31 AM:
---------------------------------------------------------

Patch v1 add ability to configure maxShare as a percentage of cluster resources.
To do that, we need to also changes {{maxChildResources}}, {{queueMaxResourcesDefault}}. The calculation of max share is done in {{FSQueue#getMaxShare()}}, which is decoupled from allocation file loading since it takes cluster resources as one input. Some checking logics also need to move from allocation file loading phase.


was (Author: yufeigu):
Patch v1 add ability to configure maxShare as a percentage of cluster resources.
To do that, we need to also changes {{maxChildResources}},
{{queueMaxResourcesDefault}}. The calculation of max share is done in
FSQueue#getMaxShare(), which is decoupled from allocation file loading since it
takes cluster resources as one input. Some logic also needs to move from
allocation file loading phase.

> Fair Scheduler :ability to optionally configure minResources and maxResources in terms of percentage
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2162
>                 URL: https://issues.apache.org/jira/browse/YARN-2162
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler, scheduler
>            Reporter: Ashwin Shankar
>            Assignee: Yufei Gu
>              Labels: scheduler
>         Attachments: YARN-2162.001.patch
>
>
> minResources and maxResources in fair scheduler configs are expressed in terms of absolute numbers X mb, Y vcores. 
> As a result, when we expand or shrink our hadoop cluster, we need to recalculate and change minResources/maxResources accordingly, which is pretty inconvenient.
> We can circumvent this problem if we can optionally configure these properties in terms of percentage of cluster capacity. 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org