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 D1C39ECEB for ; Fri, 1 Feb 2013 04:03:18 +0000 (UTC) Received: (qmail 99572 invoked by uid 500); 1 Feb 2013 04:03:18 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 99153 invoked by uid 500); 1 Feb 2013 04:03:16 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 98827 invoked by uid 99); 1 Feb 2013 04:03:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2013 04:03:14 +0000 Date: Fri, 1 Feb 2013 04:03:14 +0000 (UTC) From: "Thomas Graves (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-370) CapacityScheduler app submission fails when min alloc size not multiple of AM size MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Thomas Graves created YARN-370: ---------------------------------- Summary: CapacityScheduler app submission fails when min alloc= size not multiple of AM size Key: YARN-370 URL: https://issues.apache.org/jira/browse/YARN-370 Project: Hadoop YARN Issue Type: Bug Components: capacityscheduler Affects Versions: 3.0.0, 2.0.3-alpha Reporter: Thomas Graves Priority: Critical I was running 2.0.3-SNAPSHOT with the capacity scheduler configured with mi= nimum allocation size 1G. The AM size was set to 1.5G. I didn't specify res= ource calculator so it was using DefaultResourceCalculator. The am launch = failed with the error below: Application application_1359688216672_0001 failed 1 times due to Error laun= ching appattempt_1359688216672_0001_000001. Got exception: RemoteTrace: at = LocalTrace: org.apache.hadoop.yarn.exceptions.impl.pb.YarnRemoteExceptionPB= Impl: RemoteTrace: at LocalTrace: org.apache.hadoop.yarn.exceptions.impl.pb= .YarnRemoteExceptionPBImpl: Unauthorized request to start container. Expect= ed resource but found at or= g.apache.hadoop.yarn.factories.impl.pb.YarnRemoteExceptionFactoryPBImpl.cre= ateYarnRemoteException(YarnRemoteExceptionFactoryPBImpl.java:39) at org.apa= che.hadoop.yarn.ipc.RPCUtil.getRemoteException(RPCUtil.java:47) at org.apac= he.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.aut= horizeRequest(ContainerManagerImpl.java:383) at org.apache.hadoop.yarn.serv= er.nodemanager.containermanager.ContainerManagerImpl.startContainer(Contain= erManagerImpl.java:400) at org.apache.hadoop.yarn.api.impl.pb.service.Conta= inerManagerPBServiceImpl.startContainer(ContainerManagerPBServiceImpl.java:= 68) at org.apache.hadoop.yarn.proto.ContainerManager$ContainerManagerServic= e$2.callBlockingMethod(ContainerManager.java:83) at org.apache.hadoop.ipc.P= rotobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:454)= at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1014) at org.apache.hado= op.ipc.Server$Handler$1.run(Server.java:1735) at org.apache.hadoop.ipc.Serv= er$Handler$1.run(Server.java:1731) at java.security.AccessController.doPriv= ileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:415)= at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformati= on.java:1441) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1729)= at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) a= t sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAc= cessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newIns= tance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Const= ructor.newInstance(Constructor.java:525) at org.apache.hadoop.ipc.RemoteExc= eption.instantiateException(RemoteException.java:90) at org.apache.hadoop.i= pc.RemoteException.unwrapRemoteException(RemoteException.java:57) at org.ap= ache.hadoop.yarn.exceptions.impl.pb.YarnRemoteExceptionPBImpl.unwrapAndThro= wException(YarnRemoteExceptionPBImpl.java:123) at org.apache.hadoop.yarn.ap= i.impl.pb.client.ContainerManagerPBClientImpl.startContainer(ContainerManag= erPBClientImpl.java:109) at org.apache.hadoop.yarn.server.resourcemanager.a= mlauncher.AMLauncher.launch(AMLauncher.java:111) at org.apache.hadoop.yarn.= server.resourcemanager.amlauncher.AMLauncher.run(AMLauncher.java:255) at ja= va.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:111= 0) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor= .java:603) at java.lang.Thread.run(Thread.java:722) . Failing the applicati= on.=20 It looks like the launchcontext for the app didn't have the resources round= ed up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira