From yarn-issues-return-144516-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed May 9 00:04:04 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 40CEA18063B for ; Wed, 9 May 2018 00:04:04 +0200 (CEST) Received: (qmail 34292 invoked by uid 500); 8 May 2018 22:04:03 -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 34273 invoked by uid 99); 8 May 2018 22:04:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2018 22:04:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id AF2871A2EF1 for ; Tue, 8 May 2018 22:04:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 1xerxWz6kXPM for ; Tue, 8 May 2018 22:04:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 393565FB94 for ; Tue, 8 May 2018 22:04:01 +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 6D476E12F2 for ; Tue, 8 May 2018 22:04:00 +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 25BC92129C for ; Tue, 8 May 2018 22:04:00 +0000 (UTC) Date: Tue, 8 May 2018 22:04:00 +0000 (UTC) From: "Miklos Szegedi (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-8250) Create another implementation of ContainerScheduler to support NM overallocation 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-8250?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16468= 020#comment-16468020 ]=20 Miklos Szegedi commented on YARN-8250: -------------------------------------- Thanks for the patch,=C2=A0[~haibochen]. ContainerScheduler could be renamed DefaultContainerScheduler to give space= to extensions later. You could use conf.getClass in=C2=A0createContainerScheduler to automatical= ly verify the parent class. getContainersUtilization and updateContainersUtilization might need to be s= ynchronized or sampled (cloned). {code:java} 141=09public ContainersMonitor getContainersMonitor() { 142=09return nmContext.getContainerManager().getContainersMonitor(); 143=09}{code} Usually it is considered a better practice to return nmContext and rely on = the caller to retrieve the rest. shedQueuedOpportunisticContainers does a fifo, it might make sense to do a = lifo. =C2=A0 =C2=A0 > Create another implementation of ContainerScheduler to support NM overall= ocation > -------------------------------------------------------------------------= ------- > > Key: YARN-8250 > URL: https://issues.apache.org/jira/browse/YARN-8250 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Haibo Chen > Assignee: Haibo Chen > Priority: Major > Attachments: YARN-8250-YARN-1011.00.patch > > > YARN-6675 adds NM over-allocation support by modifying the existing Conta= inerScheduler and providing a utilizationBased resource tracker. > However, the implementation adds a lot of complexity to ContainerSchedule= r, and future tweak of over-allocation strategy based on how much container= s have been launched is even more complicated. > As such, this Jira proposes a new ContainerScheduler that always launch g= uaranteed containers immediately and queues opportunistic containers. It re= lies on a periodical check to launch opportunistic containers.=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