From yarn-issues-return-158192-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Sat Nov 17 04:24:17 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 9902B180670 for ; Sat, 17 Nov 2018 04:24:16 +0100 (CET) Received: (qmail 11461 invoked by uid 500); 17 Nov 2018 03:24:15 -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 11450 invoked by uid 99); 17 Nov 2018 03:24:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Nov 2018 03:24:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 30F30181295 for ; Sat, 17 Nov 2018 03:24:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 9RLk77LFI-mU for ; Sat, 17 Nov 2018 03:24:12 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id DC7BB60E0F for ; Sat, 17 Nov 2018 03:24:09 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 59F16E262F for ; Sat, 17 Nov 2018 03:24:09 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9451123FC2 for ; Sat, 17 Nov 2018 03:24:08 +0000 (UTC) Date: Sat, 17 Nov 2018 03:24:08 +0000 (UTC) From: "Sunil Govindan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-8149) Revisit behavior of Re-Reservation in Capacity Scheduler MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-8149?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8149: --------------------------------- Target Version/s: 3.3.0 (was: 3.2.0) Bulk update: moved all 3.2.0 non-blocker issues, please move back if it is = a blocker. > Revisit behavior of Re-Reservation in Capacity Scheduler > -------------------------------------------------------- > > Key: YARN-8149 > URL: https://issues.apache.org/jira/browse/YARN-8149 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Wangda Tan > Priority: Major > > Frankly speaking, I'm not sure why we need the re-reservation. The formul= a is not that easy to understand: > Inside: {{org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacit= y.allocator.RegularContainerAllocator#shouldAllocOrReserveNewContainer}} > {code:java} > starvation =3D re-reservation / (#reserved-container *=20 > (1 - min(requested-resource / max-alloc,=20 > max-alloc - min-alloc / max-alloc)) > should_allocate =3D starvation + requiredContainers - reservedContainers = > 0{code} > I think we should be able to remove the starvation computation, just to c= heck requiredContainers > reservedContainers should be enough. > In a large cluster, we can easily overflow re-reservation to MAX_INT, see= =C2=A0YARN-7636.=C2=A0 > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org