failed on connection exception: java.net.ConnectException: Connection refused in hive

Question

When I am running the following query in hive:

hive> select count(*) from testsql;

I am getting the following error:

Error 
FAILED: RuntimeException java.net.ConnectException: Call From impetus-1466/192.168.49.77          to impetus-1466:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused

The jps looks like:

[impadmin@impetus-1466 hadoop-1.0.3.15]$ jps
 26380 TaskTracker
 26709 Jps
 26230 JobTracker
 25943 NameNode

I started the

$ start-all.sh
$ start-dfs.sh
$ start-mapred.sh

How could this be solved?

Thanks

Your datanode and secondary name node services are not running. Try to stop all services then restart it again. If all the services are not running then you might need to format the Namenode. — Mukesh S
– Mukesh S, Commented Jul 10, 2014 at 13:29

Community · Accepted Answer · 2017-05-23 12:10:54Z

1

If you can open the http://localhost:8088/cluster but can't open http://localhost:50070/. Maybe datanode didn't start-up or namenode didn't formated.

And check hadoop.tmp.dir in core-site.xml, if it is not set, the default directory of it is /tmp, so set hadoop.tmp.dir in core-site.xml

<property>
    <name>hadoop.tmp.dir</name>
    <value>/path/to/hadoop/tmp</value>
</property>

Then stop hadoop and reformat hdfs namenode -format, then restart the hadoop.

Similar question http://localhost:50070 does not work HADOOP

edited May 23, 2017 at 12:10

CommunityBot

11 silver badge

answered Aug 26, 2016 at 5:04

GoingMyWay

17.6k33 gold badges105 silver badges153 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

GoingMyWay Over a year ago

@iviryxavyer You are welcome. I am glad to hear my answer helps.

Community · Accepted Answer · 2017-05-23 10:33:50Z

0

The reason for this is, either there are no datanodes in your cluster or the datanodes do not know their namenode. This might be the result of namenode format at least twice. The cluster id of namenode got changed but this change was not reflected to the datanodes.

The below links might be helpful: Datanode not starts correctly http://hortonworks.com/community/forums/topic/clusterid-mismatch-for-namenode-and-datanodes-in-fully-distributed-cluster/

edited May 23, 2017 at 10:33

CommunityBot

11 silver badge

answered Jun 30, 2015 at 6:20

New Contributer

5296 silver badges24 bronze badges

Collectives™ on Stack Overflow

failed on connection exception: java.net.ConnectException: Connection refused in hive

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related