Hadoop 2.6 Connecting to ResourceManager at /0.0.0.0:8032
Solution 1
This error mainly comes when hostname is not configured correctly ...Please check if hostname is configured correctly and same as you have mentioned for Resourcemanager...
Solution 2
I had faced the same problem. I solved it.
Do the Following steps.
- Start Yarn by using command: start-yarn.sh
- Check Resource Manager by using command: jps
- Add the following code to the configuration
<property>
<name>yarn.resourcemanager.address</name>
<value>127.0.0.1:8032</value>
</property>
Solution 3
I had also encountered the same issue where I was not able to submit the spark job with spark-submit.
The issue was due to the missing HADOOP_CONF_DIR path while launching the Spark job So, whenever you are submitting the job, set HADOOP_CONF_DIR to appropriate HADOOP CONF directory. Like export HADOOP_CONF_DIR=/etc/hadoop/conf
Jose Antonio
Updated on July 26, 2022Comments
-
Jose Antonio almost 2 years
I´m trying to run the following Spark example under Hadoop 2.6, but I get the following error:
INFO RMProxy: Connecting to ResourceManager at /0.0.0.0:8032 and the Client enters in a loop trying to connect. I´m running a cluster of two machines, one master and a slave.
./bin/spark-submit --class org.apache.spark.examples.SparkPi \ --master yarn-cluster \ --num-executors 3 \ --driver-memory 2g \ --executor-memory 2g \ --executor-cores 1 \ --queue thequeue \ lib/spark-examples*.jar \ 10
This is the error I get:
15/12/06 13:38:28 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable 15/12/06 13:38:29 INFO RMProxy: Connecting to ResourceManager at /0.0.0.0:8032 15/12/06 13:38:30 INFO Client: Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 15/12/06 13:38:31 INFO Client: Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 15/12/06 13:38:32 INFO Client: Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 15/12/06 13:38:33 INFO Client: Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) 15/12/06 13:38:34 INFO Client: Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
jps
hduser@master:/usr/local/spark$ jps
4930 ResourceManager 4781 SecondaryNameNode 5776 Jps 4608 DataNode 5058 NodeManager 4245 Worker 4045 Master
My /etc/host/
/etc/hosts 192.168.0.1 master 192.168.0.2 slave
The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes
-
Jose Antonio over 8 yearsThis is my /etc/hosts 192.168.0.1 master 192.168.0.2 slave # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes
-
Jose Antonio over 8 yearsMy hostname in the master machine is correct "master" and in the slave machine "slave".
-
Ravindra babu over 8 yearsDo you have # before the ip address of master and slave?
-
Jose Antonio over 8 yearsNo I don´t. I do not have any character before the IP
-
Jose Antonio over 8 yearsAnd in my yarn-site.xml, I have configured yarn.resourcemanager.hostname property with "master" value.
-
OneCricketeer about 7 yearsCould you provide more detail about which properties are "relevant" for the answer here?