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 6438610EC4 for ; Tue, 26 Nov 2013 10:30:33 +0000 (UTC) Received: (qmail 23301 invoked by uid 500); 26 Nov 2013 10:30:15 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 23178 invoked by uid 500); 26 Nov 2013 10:30:14 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 23171 invoked by uid 99); 26 Nov 2013 10:30:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Nov 2013 10:30:13 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_FILL_THIS_FORM_SHORT,T_REMOTE_IMAGE X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of orenault@hortonworks.com designates 209.85.128.171 as permitted sender) Received: from [209.85.128.171] (HELO mail-ve0-f171.google.com) (209.85.128.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Nov 2013 10:30:08 +0000 Received: by mail-ve0-f171.google.com with SMTP id pa12so3979461veb.30 for ; Tue, 26 Nov 2013 02:29:47 -0800 (PST) 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:content-type; bh=h8/szjChpv25fX6KzevdSOnsFjRz8mpt7BebG1Buev0=; b=XLlo/iqOrLdfHUEVZTlzAYhzkLHx+0Jo3CzW0O6MAZKN95ihAHYEDF0u8xYMUdwNnd 82yM1WKxqeirkUGAeoayI5u56itjiT1EaNeh8i2Oq85KiDnGs5LBPi+Bz7Zq+PABHwCW acDTqAhOakZXLvjaTX7CYA4hTuuHVwmgOFExFc1kcEOJ1evJgDdZ5w5J/T00zkRK4KWf iaPAzP4UYEbmuxsamaVqZ7lmVvUym7xqksWIllkOveLC1vzv0dz4Z2sX7TsYgElOklk4 avEVKgKiFxhVQvNJuzzwnc5khxT7n56n/D6f1QF0GPFyB7Gm9inL16V14Eage6CCgwcp J63A== X-Gm-Message-State: ALoCoQnbZEXFqxtBJUN+gXmGzUPP7URpVFycOUbeJ54PUhv7Hp5Bq0ctnydcI48lIc5GzPhgrZn9RqPG0i3eshGnZMStb74DNsay4++qefS8ybn+V5OkpB8= MIME-Version: 1.0 X-Received: by 10.58.248.198 with SMTP id yo6mr1105708vec.40.1385461787141; Tue, 26 Nov 2013 02:29:47 -0800 (PST) Received: by 10.58.34.135 with HTTP; Tue, 26 Nov 2013 02:29:47 -0800 (PST) In-Reply-To: References: Date: Tue, 26 Nov 2013 10:29:47 +0000 Message-ID: Subject: Re: default capacity scheduler only one job in running status From: Olivier Renault To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bdc8f1aac3e1d04ec11f545 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc8f1aac3e1d04ec11f545 Content-Type: text/plain; charset=US-ASCII If you're running all the job from the same user, by default, you can't take more than the value of the queue. It can be modified by setting the following in capacity-scheduler.xml yarn.scheduler.capacity.root.production.user-limit-factor 1 Olivier On 26 November 2013 09:20, ch huang wrote: > hi,maillist: > i set the following option in yarn-site.xml ,let yarn > framework to use capacity scheduler,but i submit three job,only one job in > running status,other two stay in accepted status,why ,the default queue > only 50% capacity used,i do not know why? > > > yarn.resourcemanager.scheduler.class > > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler > > -- * Olivier Renault * Solution Engineer ------------------------------ Phone: +44 7500 933 036 Email: orenault@hortonworks.com Website: http://www.hortonworks.com/ * Follow Us: * [image: photo] Latest From Our Blog: Fight Fraud with Big Data Analytics -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. --047d7bdc8f1aac3e1d04ec11f545 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

If you're running all the job from the same user, by default, you can&#= 39;t take more than the value of the queue. It can be modified by setting t= he following in capacity-scheduler.xml=A0

=A0 =A0<name>yarn.scheduler.capacity.root.production.user-limit-facto= r</name>

=A0=A0=A0<value>1</value>

=A0
Olivier


On 26 Nov= ember 2013 09:20, ch huang <justlooks@gmail.com> wrote:
hi,maillist:
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 i set the following option in yarn-s= ite.xml ,let yarn framework to use capacity scheduler,but i submit three jo= b,only one job in running status,other two stay in accepted status,why ,the= default queue only 50% capacity used,i do not know why?
=A0
<property>
=A0=A0=A0 <name>yarn.resourcemanager.schedul= er.class</name>
=A0=A0=A0 <value>org.apache.hadoop.yarn.serv= er.resourcemanager.scheduler.capacity.CapacityScheduler</value>
&l= t;/property>



--
Olivier Renault =A0 Solution Engineer
=A0
Phone: =A0 =A0 =A0 +44 7500 933 036
Email:=A0 =A0 =A0 orenault@hortonworks.com
=A0
Follow Us:

3D"photo"


CONFIDENTIALITY NOTICE
NOTICE: This message is = intended for the use of the individual or entity to which it is addressed a= nd may contain information that is confidential, privileged and exempt from= disclosure under applicable law. If the reader of this message is not the = intended recipient, you are hereby notified that any printing, copying, dis= semination, distribution, disclosure or forwarding of this communication is= strictly prohibited. If you have received this communication in error, ple= ase contact the sender immediately and delete it from your system. Thank Yo= u. --047d7bdc8f1aac3e1d04ec11f545--