QuickStart VM - Several Questions

[#1]

i am using the quickstart vm in order to test out connecting 3rd party query tools with hive.

i am trying to do this from ANOTHER vm running ms/windows 2008 where i am running my 3rd party product.

i am able to open a browser session on my vm and access the quickstart vm and run hue using the url http://192.168.209.129:8888

i can ping the quickstart vm fine.

what i cannot seem to do is establish a connection via jdbc or via the cloudera odbc driver or via another 3rd party odbc driver

i'd like to confirm the following:

#1 - the version of hive (0.10, 0.11, ?) on the quickstart vm

#2 - that the quickstart vm is using hiveserver2 versus hiveserver1

#3 - that the listening port is the default 10000

#4 - that the database is default

#5 - when using the jdbc / odbc connections whether authentication is required - if so what are those credentials

#6 - is there a way to validate that my vm can reach the hive server on the quickstart vm

----------------------------------------------------------

fyi - the cloudera odbc test returns the following:

Driver Version: V2.5.5.1006

Running connectivity tests...

Attempting connection
Failed to establish connection
SQLSTATE: HY000[Cloudera][HiveODBC] (34) Error from Hive: connect() failed: errno = 10061.

TESTS COMPLETED WITH ERROR.

my vm is NOT running a firewall and i used the iptables command to try and ensure that the cloudera image is not running a firewall service.

thank you for any assistance

[#2]

I generally use telnet to connect to a remote port to see if there is a connection. If the other VM can't connect, try the same telnet command on the QuickStart VM. (#3, #6)

This link gives the version information for everything in CDH 4.3. (#1)

I believe that the QuickStart VM is using HiveServer 1 (#2)

I'm not sure what you mean in (#4).

This link gives information about HiveServer 2 and JDBC authentication (#5)

[#3]

thanks jesse for your response and the various links.

what i don't understand is that according to the cloudera manager the hiveServer2 port is configured to be listening for connections on port 10000. i would have assumed that i could connect to that port from my vm.  however when using commands like telnet it does not connect while a port like 8888 (which hue runs on) tests ok.

when i run a 'netstat -tupln | less' command on the quickstart i get what is shown below. 

i see port 8888 listening for example but i don't see port 10000 listening. maybe there is something basic i don't understand and i apologize in advance for my ignorance.

thanks for any input.

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name   
tcp        0      0 0.0.0.0:7180                0.0.0.0:*                   LISTEN      2198/java           
tcp        0      0 0.0.0.0:50060               0.0.0.0:*                   LISTEN      2814/java           
tcp        0      0 0.0.0.0:50030               0.0.0.0:*                   LISTEN      2845/java           
tcp        0      0 0.0.0.0:7182                0.0.0.0:*                   LISTEN      2198/java           
tcp        0      0 0.0.0.0:9010                0.0.0.0:*                   LISTEN      2692/java           
tcp        0      0 0.0.0.0:8020                0.0.0.0:*                   LISTEN      2760/java           
tcp        0      0 0.0.0.0:8021                0.0.0.0:*                   LISTEN      2845/java           
tcp        0      0 0.0.0.0:50070               0.0.0.0:*                   LISTEN      2760/java           
tcp        0      0 0.0.0.0:8022                0.0.0.0:*                   LISTEN      2760/java           
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      1927/sshd           
tcp        0      0 127.0.0.1:631               0.0.0.0:*                   LISTEN      1776/cupsd          
tcp        0      0 0.0.0.0:8888                0.0.0.0:*                   LISTEN      2965/python2.6      
tcp        0      0 127.0.0.1:25                0.0.0.0:*                   LISTEN      2137/master         
tcp        0      0 0.0.0.0:50010               0.0.0.0:*                   LISTEN      2713/java           
tcp        0      0 127.0.0.1:53979             0.0.0.0:*                   LISTEN      2814/java           
tcp        0      0 0.0.0.0:50075               0.0.0.0:*                   LISTEN      2713/java           
tcp        0      0 0.0.0.0:9083                0.0.0.0:*                   LISTEN      2884/java           
tcp        0      0 0.0.0.0:8002                0.0.0.0:*                   LISTEN      2924/java           
tcp        0      0 0.0.0.0:50020               0.0.0.0:*                   LISTEN      2713/java           
tcp        0      0 0.0.0.0:2181                0.0.0.0:*                   LISTEN      2692/java           
tcp        0      0 0.0.0.0:42087               0.0.0.0:*                   LISTEN      2692/java           
tcp        0      0 127.0.0.1:9000              0.0.0.0:*                   LISTEN      2153/python         
tcp        0      0 0.0.0.0:7432                0.0.0.0:*                   LISTEN      1963/postgres       
tcp        0      0 0.0.0.0:46857               0.0.0.0:*                   LISTEN      2692/java           
tcp        0      0 127.0.0.1:9001              0.0.0.0:*                   LISTEN      2211/python         
tcp        0      0 0.0.0.0:9290                0.0.0.0:*                   LISTEN      2845/java           
tcp        0      0 0.0.0.0:50090               0.0.0.0:*                   LISTEN      2702/java           
udp        0      0 0.0.0.0:68                  0.0.0.0:*                               19818/dhclient      
udp        0      0 0.0.0.0:631                 0.0.0.0:*                               1776/cupsd 

[#4]

HiveServer2 uses 10000 for its Thrift Service (so Thrift only)

[#5]

thank you for the response.  so if i am setting up the cloudera odbc driver for hive in order to connect to the hive environment on the quickstart vm what port no# should i be using?  all references that i can find indicate the default is usually 10000.  if that is not the right port on the quickstart is there somewhere where i can find out what it should be?

[#6]

thanks for the link to the video. 

i can run hive commands locally on the quickstart vm so i know that hadoop / hive is installed and configuredi and running which is the great thing about using the vm.

what i want to be able to do is use hive on the quickstart from a jdbc / odbc connection running on another platform.

i have gotten an odbc connection to the quickstart vm working using the cloudera odbc driver for impala by connecting to the host and port 21050.

what has continued to allude me is being able to connect to the quickstart vm using the cloudera odbc driver for apache hive by connecting to the same host but using a port that would connect me to hive. the default port is stated to be 10000 but it does not appear that anything is listening on that port.

i can run hive and hive commands locally on the quickstart with no problem.

any ideas would be welcome particularly from anyone familiar with the setup on the quickstart vm.

thanks again to all who have responded.

[#7]

Hi

I have exactly the same problem.

ODBC for Impala works fine.

But i cannot get ODBC for Hive to work with the Quickstart VM.

Any ideas would be welcomed.

[#8]

well in one way i'm glad to see that i am not the only one.  however i still haven't found an answer.

[#9]

Well, I've put it aside for now, i am using Hortonworks Sandbox instead; but at some point i must have Cloudera to work.

[#10]

I have found the solution in another thread in this forum (https://community.cloudera.com/t5/Cloudera-Manager-Installation/Cannot-connect-to-Hive-on-CDH4-5-EC2...

You have to setup and start the HiveServer2-service in Cloudera Manager. It is not active by default in the VM-image.

Now the ODBC-driver works fine against HiveServer2.

The irritating thing is that this thread is actually reffered to in the other thread.