Hi,

 

I have set up hiverserv2 running on port 10010 and I can use beeline from
remote host to connect to the server host

 

beeline -u jdbc:hive2://rhes564:10010/default
org.apache.hive.jdbc.HiveDriver -n hduser -p xxxxx

scan complete in 5ms

Connecting to jdbc:hive2://rhes564:10010/default

SLF4J: Class path contains multiple SLF4J bindings.

SLF4J: Found binding in
[jar:file:/home/hduser/hadoop/hadoop-2.6.0/share/hadoop/common/lib/slf4j-log
4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: Found binding in
[jar:file:/usr/lib/hive/lib/hive-jdbc-0.14.0-standalone.jar!/org/slf4j/impl/
StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.

SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

Connected to: Apache Hive (version 0.14.0)

Driver: Hive JDBC (version 0.14.0)

Transaction isolation: TRANSACTION_REPEATABLE_READ

Beeline version 0.14.0 by Apache Hive

 

 

That works fine. On the namenode I can do

 

hdfs dfs -ls hdfs://rhes564:9000/user/hive

Found 1 items

drwxrwxrwx   - hduser supergroup          0 2015-03-09 10:48
hdfs://rhes564:9000/user/hive/warehouse

 

However, on the remote host I cannot do the same!

 

hdfs dfs -ls hdfs://rhes564:9000/user/hive

ls: Call From rhes5/50.140.197.216 to rhes564:9000 failed on connection
exception: java.net.ConnectException: Connection refused; For more details
see:  http://wiki.apache.org/hadoop/ConnectionRefused

 

Obviously this is not a firewall blocking etc.  Appreciate any feed back.

 

Mich

 

NOTE: The information in this email is proprietary and confidential. This
message is for the designated recipient only, if you are not the intended
recipient, you should destroy it immediately. Any information in this
message shall not be understood as given or endorsed by Peridale Ltd, its
subsidiaries or their employees, unless expressly so stated. It is the
responsibility of the recipient to ensure that this email is virus free,
therefore neither Peridale Ltd, its subsidiaries nor their employees accept
any responsibility.

 

Reply via email to