Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9CB49200BE5 for ; Sat, 24 Dec 2016 19:24:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9B69E160B1E; Sat, 24 Dec 2016 18:24:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E6F26160B2F for ; Sat, 24 Dec 2016 19:23:59 +0100 (CET) Received: (qmail 10440 invoked by uid 500); 24 Dec 2016 18:23:58 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 10089 invoked by uid 99); 24 Dec 2016 18:23:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 Dec 2016 18:23:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 649F42C2A67 for ; Sat, 24 Dec 2016 18:23:58 +0000 (UTC) Date: Sat, 24 Dec 2016 18:23:58 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (YARN-6021) When your allocated minShare of all queue`s added up exceed cluster capacity you can get some queue for 0 fairshare MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 24 Dec 2016 18:24:00 -0000 [ https://issues.apache.org/jira/browse/YARN-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-6021. ------------------------------------ Resolution: Not A Problem I am closing this as "Not a Problem". Please reopen it if this is indeed an issue. > When your allocated minShare of all queue`s added up exceed cluster capacity you can get some queue for 0 fairshare > ------------------------------------------------------------------------------------------------------------------- > > Key: YARN-6021 > URL: https://issues.apache.org/jira/browse/YARN-6021 > Project: Hadoop YARN > Issue Type: Bug > Components: fairscheduler > Affects Versions: 2.4.0 > Reporter: Feng Yuan > Assignee: Feng Yuan > Priority: Critical > > In fair-scheduler.xml,If you config the minshare add up exceed parentQueue`s fairshare,for root`s childs,fairshare is cluster capacity. > You will found your R value look like below when compute childs fairshares: > 1.0 > 0.5 > 0.25 > 0.125 > 0.0625 > 0.03125 > 0.015625 > 0.0078125 > 0.00390625 > I find this is due to: > double rMax = 1.0; > while (resourceUsedWithWeightToResourceRatio(rMax, schedulables, type) > < totalResource) { > rMax *= 2.0; > } > because resourceUsedWithWeightToResourceRatio will add minShare together. > As i think is really should we bring in minShare when compute fairshare? > My advice is we just consider weight is enough,and minshare's guarantee > will get fulfill when assginContainer! > Hope suggestion! -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org