Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Guys, I was able to fix this issue but trail and error not sure which property made it work :) but its working and i have to use 8032 as jobtracker. I also restarted all the components before i was only restarting nodemanager and resource manager after property update. You get this error if you

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Thank you all, I have updated my oozie job.properties to use 8030 and now i am getting below error 2016-08-22 17:22:02,893 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService: NodeManager from node slave03(cmPort: 40511 httpPort: 8042) registered with capability:

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

HI Ram RM logs looks fine and as per config it looks like RM is running on 8030 itself. I am not very sure about the oozie end config which you mentioned. I suggest you could check the config end more and debug there. Also will let other community folks to pitch in if they have some other

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

any thoughts from the logs and config I have shared? On Aug 21, 2016 8:32 AM, "rammohan ganapavarapu" wrote: > so in job.properties what is the jobtracker property, is it RM ip: port or > scheduler port which is 8030, if I use 8030 I am getting unknown protocol > proto

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

so in job.properties what is the jobtracker property, is it RM ip: port or scheduler port which is 8030, if I use 8030 I am getting unknown protocol proto buffer error. On Aug 21, 2016 7:37 AM, "Sunil Govind" wrote: > Hi. > > It seems its an oozie issue. From conf, RM

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Hi. It seems its an oozie issue. From conf, RM scheduler is running at port 8030. But your job.properties is taking 8032. I suggest you could double confirm your oozie configuration and see the configurations are intact to contact RM. Sharing a link also

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Hi Ram >From the console log, as Rohith said, AM is looking for AM at 8030. So pls confirm the RM port once. Could you please share AM and RM logs. Thanks Sunil On Sat, Aug 20, 2016 at 10:36 AM rammohan ganapavarapu < rammohanga...@gmail.com> wrote: > yes, I did configured. > > On Aug 19, 2016

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

yes, I did configured. On Aug 19, 2016 7:22 PM, "Rohith Sharma K S" wrote: > Hi > > From below discussion and AM logs, I see that AM container has launched > but not able to connect to RM. > > This looks like your configuration issue. Would you check your job.xml jar >

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Hi From below discussion and AM logs, I see that AM container has launched but not able to connect to RM. This looks like your configuration issue. Would you check your job.xml jar that does yarn.resourcemanager.scheduler.address has been configured? Essentially, this address required by

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Even if the cluster dont have enough resources it should connect to " /0.0.0.0:8030" right? it should connect to my , not sure why its trying to connect to 0.0.0.0:8030. I have verified the config and i removed traces of 0.0.0.0 still no luck. org.apache.hadoop.yarn.client.RMProxy: Connecting

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

When i submit a job using yarn its seems working only with oozie its failing i guess, not sure what is missing. yarn jar /uap/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.7.1.jar pi 20 1000 Number of Maps = 20 Samples per Map = 1000 . . . Job Finished in 19.622 seconds Estimated

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Do you know what properties to tune? Thanks, Ram On Thu, Aug 18, 2016 at 9:11 PM, tkg_cangkul wrote: > i think that's because you don't have enough resource. u can tune your > cluster config to maximize your resource. > > > On 19/08/16 11:03, rammohan ganapavarapu

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

i think that's because you don't have enough resource. u can tune your cluster config to maximize your resource. On 19/08/16 11:03, rammohan ganapavarapu wrote: I dont see any thing odd except this not sure if i have to worry about it or not. 2016-08-19 03:29:26,621 INFO [main]

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

maybe u can check the logs from port 8088 on your browser. that was RM UI. just choose your job id and then check the logs. On 19/08/16 10:14, rammohan ganapavarapu wrote: Sunil, Thanks you for your input, below are my server metrics for RM. Also attached RM UI for capacity scheduler

Re: ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Hi It could be because of many of reasons. Also I am not sure about which scheduler your are using, pls share more details such as RM log etc. I could point out few reasons - Such as "Not enough resource is cluster" can cause this - If using Capacity Scheduler, if queue capacity is maxed out,

ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Hi, When i submit a MR job, i am getting this from AM UI but it never get finished, what am i missing ? Thanks, Ram