Re: Namenode Unable to Authenticate to QJM in Secure mode.

2016-08-19 Thread Rakesh Radhakrishnan
Hi Akash, In general "GSSException: No valid credentials provided" means you don’t have valid Kerberos credentials. I'm suspecting some issues related to spnego, could you please revisit all of your kerb related configurations, probably you can start from the below configuration. Please share *-si

Re: hfs downgrade from 2.7.2 to 2.5.0

2016-08-19 Thread Chris Nauroth
Hello Jin, 1. I believe there may have been a recent bug around slow DataNode upgrade times, but I can’t find the relevant JIRA issue right now. Perhaps someone else on the list remembers. HDFS-8791 is relevant to performance of the block layout on disk in versions 2.6.0 and later, but I vagu

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

2016-08-19 Thread rammohan ganapavarapu
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 valu

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

2016-08-19 Thread rammohan ganapavarapu
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 t

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

2016-08-19 Thread Rohith Sharma K S
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 MRAp

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

2016-08-19 Thread rammohan ganapavarapu
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 > that does *yarn.resourcema

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

2016-08-19 Thread Sunil Govind
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