Hello,
Performing a map-reduce simple test I have seen that port 8030 is working
properly (so I think the ResourceManager in logs is job.scheduler process)
I've runned a map-reduce job simply using hadoop command:
hadoop jar <jarFile> <MainClass> <hdfsInputDirectory>
<hdfsOutputDirectory>
and in systemlogs of nodemanager the following line is shown:
2013-11-19 12:33:16,267 INFO [main]
org.apache.hadoop.yarn.client.RMProxy: Connecting to ResourceManager at
mvalle1/192.168.0.4:8030
Can you help my to understand why running a job using hadoop command takes
the right job.scheduler adress and port (mvalle1/192.168.0.4:8030) and
oozie jobs take it wrong (/0.0.0.0:8030).
Thanks for help.
2013/11/14 Mona Chitnis <[email protected]>
> Check your port number for the 'jobtracker' address, that you may be
> passing in your job.properties. Is your Resourcemanager running on port
> 8030? Change it to the correct value
>
> On 11/14/13 8:15 AM, "Marcelo Valle" <[email protected]> wrote:
>
> >Hello,
> >
> >I'm new with Ozzie and I'm triying to execute the map reduce job example
> >in
> >Hadoop 2.2.0
> >
> >I followed the following steps:
> >
> >hdfs dfs -put examples examples
> >bin/oozie job -oozie http://localhost:11000/oozie -config
> >examples/apps/map-reduce/job.properties -run
> >
> >After that I can see the work RUNNING in Ozzie web interface
> >In Hadoop Resource Manager Interface the work is in ACCEPTED state, but
> >after few minutes the status change to KILLED, so the Map Reduce job is
> >not
> >finishing ok.
> >
> >In datanode logs the following lines are repeated several times:
> >
> >INFO [main] org.apache.hadoop.yarn.client.RMProxy: Connecting to
> >ResourceManager at /0.0.0.0:8030
> >INFO [main] org.apache.hadoop.ipc.Client: Retrying connect to server:
> >0.0.0.0/0.0.0.0:8030. Already tried 0 time(s); retry policy is
> >RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1
> >SECONDS)
> >
> >
> >Can you help to bring us to the right direction?
> >
> >
> >Thanks in advance!
>
>
