From yarn-issues-return-152370-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Thu Aug 30 14:39:05 2018 Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B66DC1EED9 for ; Thu, 30 Aug 2018 14:39:05 +0000 (UTC) Received: (qmail 72032 invoked by uid 500); 30 Aug 2018 14:39:05 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 71974 invoked by uid 500); 30 Aug 2018 14:39:05 -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 71963 invoked by uid 99); 30 Aug 2018 14:39:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Aug 2018 14:39:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 159A6C6E9D for ; Thu, 30 Aug 2018 14:39:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, 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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id RjrEvV257l-V for ; Thu, 30 Aug 2018 14:39:03 +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 3FA3C5F612 for ; Thu, 30 Aug 2018 14:39:02 +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 76E4EE263A for ; Thu, 30 Aug 2018 14:39:01 +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 992F626B68 for ; Thu, 30 Aug 2018 14:39:00 +0000 (UTC) Date: Thu, 30 Aug 2018 14:39:00 +0000 (UTC) From: =?utf-8?Q?Antal_B=C3=A1lint_Steinbach_=28JIRA=29?= To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-8468) Limit container sizes per queue in FairScheduler 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-8468?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Antal B=C3=A1lint Steinbach updated YARN-8468: ----------------------------------------- Attachment: YARN-8468.010.patch > Limit container sizes per queue in FairScheduler > ------------------------------------------------ > > Key: YARN-8468 > URL: https://issues.apache.org/jira/browse/YARN-8468 > Project: Hadoop YARN > Issue Type: Improvement > Components: fairscheduler > Affects Versions: 3.1.0 > Reporter: Antal B=C3=A1lint Steinbach > Assignee: Antal B=C3=A1lint Steinbach > Priority: Critical > Attachments: YARN-8468.000.patch, YARN-8468.001.patch, YARN-8468.= 002.patch, YARN-8468.003.patch, YARN-8468.004.patch, YARN-8468.005.patch, Y= ARN-8468.006.patch, YARN-8468.007.patch, YARN-8468.008.patch, YARN-8468.009= .patch, YARN-8468.010.patch > > > When using any scheduler, you can use "yarn.scheduler.maximum-allocation-= mb" to limit the overall size of a container. This applies globally to all = containers and cannot be limited by queue or and is not scheduler dependent= . > =C2=A0 > The goal of this ticket is to allow this value to be set on a per queue b= asis. > =C2=A0 > The use case: User has two pools, one for ad hoc jobs and one for enterpr= ise apps. User wants to limit ad hoc jobs to small containers but allow ent= erprise apps to request as many resources as needed. Setting yarn.scheduler= .maximum-allocation-mb sets a default value for maximum container size for = all queues and setting maximum resources per queue with =E2=80=9CmaxContain= erResources=E2=80=9D queue config value. > =C2=A0 > Suggested solution: > =C2=A0 > All the infrastructure is already in the code. We need to do the followin= g: > * add the setting to the queue properties for all queue types (parent an= d leaf), this will cover dynamically created queues. > * if we set it on the root we override the scheduler setting and we shou= ld not allow that. > * make sure that queue resource cap can not be larger than scheduler max= resource cap in the config. > * implement=C2=A0getMaximumResourceCapability(String queueName)=C2=A0in = the FairScheduler > * implement=C2=A0getMaximumResourceCapability()=C2=A0in both FSParentQue= ue and FSLeafQueue as follows > * expose the setting in the queue information in the RM web UI. > * expose the setting in the metrics etc for the queue. > * write JUnit tests. > * update the scheduler documentation. -- 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