Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C538D19682 for ; Fri, 15 Apr 2016 10:42:39 +0000 (UTC) Received: (qmail 17127 invoked by uid 500); 15 Apr 2016 10:42:35 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 16985 invoked by uid 500); 15 Apr 2016 10:42:35 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 16974 invoked by uid 99); 15 Apr 2016 10:42:34 -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; Fri, 15 Apr 2016 10:42:34 +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 6DFFC180317 for ; Fri, 15 Apr 2016 10:42:34 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.181 X-Spam-Level: * X-Spam-Status: No, score=1.181 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=2, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=handybook.com 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 tG2M7hlTtN1W for ; Fri, 15 Apr 2016 10:42:32 +0000 (UTC) Received: from mail-vk0-f49.google.com (mail-vk0-f49.google.com [209.85.213.49]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id E89FF5F5CB for ; Fri, 15 Apr 2016 10:42:31 +0000 (UTC) Received: by mail-vk0-f49.google.com with SMTP id n62so26095362vkb.0 for ; Fri, 15 Apr 2016 03:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=handybook.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=YYhmlwtjK6FZ/3SCAIsWkwETUTHaFVjZCpk+ADbe7n4=; b=Sc11ds8VRBue5v3EROqX7Nk/uCDqZfZopy9s3sNuSsfggO9caxZpOTfioiK2SVNY9N GFMLZ3aNhpj6LJKZi8i/51W1d4otxOI+723ViRaJ+n2KUeBakvBPSinBiaYxUO+jmZGA YP3G6W86faZagw3PCmF5mnUHqADKqtdjhVDBM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=YYhmlwtjK6FZ/3SCAIsWkwETUTHaFVjZCpk+ADbe7n4=; b=ldaVffgf2bCvnYCVrsr01GjPguQ+Xx+MMKdgekqXrc4EwUecCWjSANtlctBpOWPneT sWH+N4y8KULN5HXeRtKb/zqNPJys0AUBtRunsxPGdXE4IgAY0gvq3IDWLGtyFaP82Icv dDiDKTZxShrU6xH+IKeZ28AaEVXW20ST9koOYqnyYXflzDWCsmzbjEVcJWcSPjUYzZK7 3djvhcpEc0ELZ1vrjCTkOEcSTy1yw9fcHHiQ5Y3aOKqgi/uSYGGXnU3CPXgJ+pAMjQWP DklVxD5kVEB6XaoTyBdqsBcBLdB1oI1i6neFEEiyJg3XcuDpqKiqowJThUz6vZrBiIzS /Qow== X-Gm-Message-State: AOPr4FXZT01TfJzT46C6x1HKQ2SX9fPbR+9LPbWXPwUhrBZPQ1QxuS8au3n0/gcAN2fX2MxlGGAufOnTN/LhsFRn4aSpx/pzQo++SulThq0ZkQi7e6Gr5OFn4ekwDvKoqmF3a51vzipFgC6KPiRzZnVYYancNAQopj3D1/q9wB+txOT4y+Z5Opd4xtEaod2+9K9oSxtqkG4TjFzrcg== MIME-Version: 1.0 X-Received: by 10.176.65.73 with SMTP id j67mr10133720uad.24.1460716951303; Fri, 15 Apr 2016 03:42:31 -0700 (PDT) Received: by 10.31.227.132 with HTTP; Fri, 15 Apr 2016 03:42:31 -0700 (PDT) In-Reply-To: References: Date: Fri, 15 Apr 2016 06:42:31 -0400 Message-ID: Subject: About Yarn Capacity Scheduler and Fair Scheduler From: Marcin Tustin To: Todd Cc: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=94eb2c123b10001628053083ab88 --94eb2c123b10001628053083ab88 Content-Type: text/plain; charset=UTF-8 This is what the capacity scheduler is for. See my article on working around a particular bug in the current version of the capacity scheduler https://medium.com/handy-tech/practical-capacity-scheduling-with-yarn-28548ae4fb88 Note the part on user limits. On Friday, April 15, 2016, Todd > wrote: > Hi, > > I am kind of new to Yarn scheduler , I have a requirement that, we have > vip users and normal users, we want vip users to have available resources > whenever they submit applications so that vip users don't have to wait > normal users to release their resources > > Do Capacity Scheduler and Fair Scheduler support this scenario? > Thanks in advance! > -- Want to work at Handy? Check out our culture deck and open roles Latest news at Handy Handy just raised $50m led by Fidelity --94eb2c123b10001628053083ab88 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This is what the capacity scheduler is for.=C2=A0

= See my article on working around a particular bug in the current ver= sion of the capacity scheduler=C2=A0https://medium.com/= handy-tech/practical-capacity-scheduling-with-yarn-28548ae4fb88

Note the part on user limits.=C2=A0

O= n Friday, April 15, 2016, Todd <bit1129@163.com&g= t; wrote:
Hi,

I am kind of= new to Yarn scheduler , I have a requirement that, we have vip users and n= ormal users, we want vip users to have available resources whenever they su= bmit applications so that vip users don't have to wait normal users to = release their resources

Do Capacity Scheduler and Fair Scheduler sup= port this scenario?
Thanks in advance!

Want to work at Han= dy? Check out our=C2=A0culture deck and open r= oles
Latest=C2=A0news=C2= =A0at Handy
Handy=C2=A0just raised $50m=C2=A0led by Fidelity

--94eb2c123b10001628053083ab88--