Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 6041E102E6 for ; Tue, 26 Nov 2013 12:38:23 +0000 (UTC) Received: (qmail 50129 invoked by uid 500); 26 Nov 2013 12:38:14 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 49798 invoked by uid 500); 26 Nov 2013 12:38:08 -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 Delivered-To: moderator for user@hadoop.apache.org Received: (qmail 27217 invoked by uid 99); 26 Nov 2013 09:35:57 -0000 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=8jdZSpmPWXqz5eQxIx8Wn1R0wXEdhJGEMVQXFkkO5Bc=; b=emNv5VzBHLvd7ZhgweDXhJKw16nlgIcgRSZBVzctb/3bgajdqb3qlvoLkZRyMgkE3z 4ShwvtXPpeXCx8frwJz0plwiV+Ik6quANE2pgmzdV3gFnl+isly+4qfXZJ1XaC+Dr3CT /mhEaTVWKhr03Pgkrd+6udi7e/KqHHY57uCJ/FriT+qdbwHrFvVF77Zm/mMovCW0TdMe SalOicUyVWMIfsR7vHY6152cbfNiqQeRV1K0lcbMuN3Q5mYCNi/ul01G8ImurwgxkEzz Pw9qmlKiYfBuIo2euoK34EMFrjRBBIpb1Hkkw8mAQQqwLKBxPfaF/NucPCGSBpQYWYgX Q21Q== MIME-Version: 1.0 X-Received: by 10.182.103.133 with SMTP id fw5mr9513431obb.43.1385458555711; Tue, 26 Nov 2013 01:35:55 -0800 (PST) In-Reply-To: References: Date: Tue, 26 Nov 2013 15:05:55 +0530 Message-ID: Subject: Re: default capacity scheduler only one job in running status From: Devaraj K To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=089e01184702107a2d04ec11351f --089e01184702107a2d04ec11351f Content-Type: text/plain; charset=ISO-8859-1 Could you check the below configuration in capacity-scheduler.xml, whether is it causing to run only one AM. yarn.scheduler.capacity.maximum-am-resource-percent 0.1 Maximum percent of resources in the cluster which can be used to run application masters i.e. controls number of concurrent running applications. On Tue, Nov 26, 2013 at 2:50 PM, 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 > > -- Thanks Devaraj K --089e01184702107a2d04ec11351f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Could you check the below configuration in capacity-s= cheduler.xml, whether is it causing to run only one AM. =A0

<= /div>
<property>
=A0 =A0 <name>yarn.scheduler.cap= acity.maximum-am-resource-percent</name>
=A0 =A0 <value>0.1</value>
=A0 =A0 <descripti= on>
=A0 =A0 =A0 Maximum percent of resources in the cluster wh= ich can be used to run=A0
=A0 =A0 =A0 application masters i.e. co= ntrols number of concurrent running
=A0 =A0 =A0 applications.
=A0 =A0 </description>
=
=A0 </property>


On Tue, Nov 26, 2013 at 2:50 PM, 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>



--


Thanks
Devaraj K
--089e01184702107a2d04ec11351f--