Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of jayunit100@gmail.com designates
 209.85.215.53 as permitted sender)
MIME-Version: 1.0
Date: Thu, 24 Apr 2014 16:23:23 -0400
Message-ID: 
 <CAAu13zFjFt21qVmPuuDYkEkL9FG7NKNvQGWZoPEAUUL+WL7T+g@mail.gmail.com>
Subject: Yarn hangs @Scheduled
From: Jay Vyas <jayunit100@gmail.com>
To: "common-user@hadoop.apache.org" <user@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=089e013d100aebd99704f7cf9e9d

--089e013d100aebd99704f7cf9e9d
Content-Type: text/plain; charset=UTF-8

Hi folks :  My yarn jobs seem to be hanging in the "SHEDULED" state.  I've
restarted my nodemanager a few times , but no luck.

What are the possible reasons that YARN job submission hangs ?  I know one
is resource availability, but this is a fresh cluster on a VM with only one
job, one NM, and one RM.

14/04/24 16:20:32 INFO ipc.Server: Auth successful for
yarn@IDH1.LOCAL(auth:SIMPLE)
14/04/24 16:20:32 INFO authorize.ServiceAuthorizationManager: Authorization
successful for yarn@IDH1.LOCAL (auth:KERBEROS) for protocol=interface
org.apache.hadoop.yarn.api.ApplicationClientProtocolPB
14/04/24 16:20:32 INFO resourcemanager.ClientRMService: Allocated new
applicationId: 4
14/04/24 16:20:33 INFO resourcemanager.ClientRMService: Application with id
4 submitted by user yarn
14/04/24 16:20:33 INFO resourcemanager.RMAuditLogger: USER=yarn
IP=192.168.122.100      OPERATION=Submit Application Request
TARGET=ClientRMService  RESULT=SUCCESS  APPID=application_1398370674313_0004
14/04/24 16:20:33 INFO rmapp.RMAppImpl: Storing application with id
application_1398370674313_0004
14/04/24 16:20:33 INFO rmapp.RMAppImpl: application_1398370674313_0004
State change from NEW to NEW_SAVING
14/04/24 16:20:33 INFO recovery.RMStateStore: Storing info for app:
application_1398370674313_0004
14/04/24 16:20:33 INFO rmapp.RMAppImpl: application_1398370674313_0004
State change from NEW_SAVING to SUBMITTED
14/04/24 16:20:33 INFO fair.FairScheduler: Accepted application
application_1398370674313_0004 from user: yarn, in queue: default,
currently num of applications: 4
14/04/24 16:20:33 INFO rmapp.RMAppImpl: application_1398370674313_0004
State change from SUBMITTED to ACCEPTED
14/04/24 16:20:33 INFO resourcemanager.ApplicationMasterService:
Registering app attempt : appattempt_1398370674313_0004_000001
14/04/24 16:20:33 INFO attempt.RMAppAttemptImpl:
appattempt_1398370674313_0004_000001 State change from NEW to SUBMITTED
14/04/24 16:20:33 INFO fair.FairScheduler: Added Application Attempt
appattempt_1398370674313_0004_000001 to scheduler from user: yarn
14/04/24 16:20:33 INFO attempt.RMAppAttemptImpl:
appattempt_1398370674313_0004_000001 State change from SUBMITTED to
SCHEDULED


-- 
Jay Vyas
http://jayunit100.blogspot.com

--089e013d100aebd99704f7cf9e9d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi folks :=C2=A0 My yarn jobs seem to be hanging in the &q=
uot;SHEDULED&quot; state.=C2=A0 I&#39;ve restarted my nodemanager a few tim=
es , but no luck.=C2=A0 <br><br>What are the possible reasons that YARN job=
 submission hangs ?=C2=A0 I know one is resource availability, but this is =
a fresh cluster on a VM with only one job, one NM, and one RM.=C2=A0 <br>
<div><br>14/04/24 16:20:32 INFO ipc.Server: Auth successful for yarn@IDH1.L=
OCAL (auth:SIMPLE)<br>14/04/24 16:20:32 INFO authorize.ServiceAuthorization=
Manager: Authorization successful for yarn@IDH1.LOCAL (auth:KERBEROS) for p=
rotocol=3Dinterface org.apache.hadoop.yarn.api.ApplicationClientProtocolPB<=
br>
14/04/24 16:20:32 INFO resourcemanager.ClientRMService: Allocated new appli=
cationId: 4<br>14/04/24 16:20:33 INFO resourcemanager.ClientRMService: Appl=
ication with id 4 submitted by user yarn<br>14/04/24 16:20:33 INFO resource=
manager.RMAuditLogger: USER=3Dyarn IP=3D192.168.122.100=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 OPERATION=3DSubmit Application Request=C2=A0=C2=A0=C2=A0 TARGE=
T=3DClientRMService=C2=A0 RESULT=3DSUCCESS=C2=A0 APPID=3Dapplication_139837=
0674313_0004<br>
14/04/24 16:20:33 INFO rmapp.RMAppImpl: Storing application with id applica=
tion_1398370674313_0004<br>14/04/24 16:20:33 INFO rmapp.RMAppImpl: applicat=
ion_1398370674313_0004 State change from NEW to NEW_SAVING<br>14/04/24 16:2=
0:33 INFO recovery.RMStateStore: Storing info for app: application_13983706=
74313_0004<br>
14/04/24 16:20:33 INFO rmapp.RMAppImpl: application_1398370674313_0004 Stat=
e change from NEW_SAVING to SUBMITTED<br>14/04/24 16:20:33 INFO fair.FairSc=
heduler: Accepted application application_1398370674313_0004 from user: yar=
n, in queue: default, currently num of applications: 4<br>
14/04/24 16:20:33 INFO rmapp.RMAppImpl: application_1398370674313_0004 Stat=
e change from SUBMITTED to ACCEPTED<br>14/04/24 16:20:33 INFO resourcemanag=
er.ApplicationMasterService: Registering app attempt : appattempt_139837067=
4313_0004_000001<br>
14/04/24 16:20:33 INFO attempt.RMAppAttemptImpl: appattempt_1398370674313_0=
004_000001 State change from NEW to SUBMITTED<br>14/04/24 16:20:33 INFO fai=
r.FairScheduler: Added Application Attempt appattempt_1398370674313_0004_00=
0001 to scheduler from user: yarn<br>
14/04/24 16:20:33 INFO attempt.RMAppAttemptImpl: appattempt_1398370674313_0=
004_000001 State change from SUBMITTED to SCHEDULED<br><br><br><br clear=3D=
"all"><br>-- <br>Jay Vyas<br><a href=3D"http://jayunit100.blogspot.com" tar=
get=3D"_blank">http://jayunit100.blogspot.com</a>
</div></div>

--089e013d100aebd99704f7cf9e9d--