From yarn-issues-return-154807-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Tue Oct 9 11:01:09 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 6E409180668 for ; Tue, 9 Oct 2018 11:01:08 +0200 (CEST) Received: (qmail 21935 invoked by uid 500); 9 Oct 2018 09:01:07 -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 21924 invoked by uid 99); 9 Oct 2018 09:01:07 -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; Tue, 09 Oct 2018 09:01:07 +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 09A68180A78 for ; Tue, 9 Oct 2018 09:01:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id k3cSqipXjgw1 for ; Tue, 9 Oct 2018 09:01:02 +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 DE2175F41C for ; Tue, 9 Oct 2018 09:01: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 F39E9E2635 for ; Tue, 9 Oct 2018 09:01: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 509B924817 for ; Tue, 9 Oct 2018 09:01:00 +0000 (UTC) Date: Tue, 9 Oct 2018 09:01: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] [Comment Edited] (YARN-8468) Enable the use of queue based maximum container allocation limit and implement it 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:comment-tabpanel&focusedCommentId=3D16642= 924#comment-16642924 ]=20 Antal B=C3=A1lint Steinbach edited comment on YARN-8468 at 10/9/18 9:00 AM: ----------------------------------------------------------------------- Hi [~cheersyang] , Yes, it is related. I fixed it in the new patch. The problem was that the c= ustom=C2=A0resource type parse in=C2=A0AllocationFileLoaderService was is n= ot working in this version like in trunk. I removed the custom resource typ= e from the test. It looks like branch-3.2 already contains this commit. So there is no=C2=A0= need for another patch. Thanks was (Author: bsteinbach): Hi [~cheersyang] , Yes, it is related. I fixed it in the new patch. The problem was that the c= ustom=C2=A0resource type parse in=C2=A0AllocationFileLoaderService was is n= ot working in this version like in trunk. I removed the custom resource typ= e from the test. I will upload the patch for branch-3.2 soon. Thanks > Enable the use of queue based maximum container allocation limit and impl= ement it in FairScheduler > -------------------------------------------------------------------------= ------------------------- > > Key: YARN-8468 > URL: https://issues.apache.org/jira/browse/YARN-8468 > Project: Hadoop YARN > Issue Type: Improvement > Components: fairscheduler, scheduler > Affects Versions: 3.1.0 > Reporter: Antal B=C3=A1lint Steinbach > Assignee: Antal B=C3=A1lint Steinbach > Priority: Critical > Fix For: 3.2.0 > > Attachments: YARN-8468-branch-3.1.018.patch, YARN-8468-branch-3.1= .019.patch, YARN-8468.000.patch, YARN-8468.001.patch, YARN-8468.002.patch, = YARN-8468.003.patch, YARN-8468.004.patch, YARN-8468.005.patch, YARN-8468.00= 6.patch, YARN-8468.007.patch, YARN-8468.008.patch, YARN-8468.009.patch, YAR= N-8468.010.patch, YARN-8468.011.patch, YARN-8468.012.patch, YARN-8468.013.p= atch, YARN-8468.014.patch, YARN-8468.015.patch, YARN-8468.016.patch, YARN-8= 468.017.patch, YARN-8468.018.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= . > The goal of this ticket is to allow this value to be set on a per queue b= asis. > 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. > Suggested solution: > 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(String queueName)=C2=A0in = both FSParentQueue 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. > * Enforce the use of queue based maximum allocation limit if it is avail= able, if not use the general scheduler level setting > ** Use it during validation and normalization of requests in scheduler.a= llocate, app submit and resource request -- 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