Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Impala-Shell error

Impala-Shell error

New Contributor

Hi,

 

  Recently I downloaded the QuickStart VM and installed the impala components including the server and store and after starting the server and store when I started the impala-shell, it was throwing a following error.

 

 "Error connecting: <class 'thrift.transport.TTransport.TTransportException'>, Could not connect to localhost.localdomain:21000".

 

1)  Please have a look at some of my investigations:

   [cloudera@localhost ~]$ ps -ef | grep impala
impala    9603     1  0 22:30 ?        00:00:00 /usr/lib/impala/sbin/statestored -log_dir=/var/log/impala -state_store_port=24000
impala   17027     1 90 23:22 ?        00:00:07 /usr/lib/impala/sbin/impalad -log_dir=/var/log/impala -state_store_port=24000 -use_statestore -state_store_host=127.0.0.1 -be_port=22000


2) [cloudera@localhost ~]$ cat /var/log/impala/impala-server.log
E0925 22:31:08.305951  9691 Log4JLogger.java:115] Bundle "org.eclipse.jdt.core" requires "org.eclipse.core.resources" but it cannot be resolved.
E0925 22:31:08.306408  9691 Log4JLogger.java:115] Bundle "org.eclipse.jdt.core" requires "org.eclipse.core.runtime" but it cannot be resolved.
E0925 22:31:08.306602  9691 Log4JLogger.java:115] Bundle "org.eclipse.jdt.core" requires "org.eclipse.text" but it cannot be resolved.
E0925 23:03:32.119632  9691 impala-server.cc:339] Could not read the HDFS root directory at hdfs://localhost.localdomain:8020. Error was:
Call From localhost.localdomain/16.110.135.52 to localhost.localdomain:8020 failed on socket timeout exception: org.apache.hadoop.net.ConnectTimeoutException: 20000 millis timeout while waiting for channel to be ready for connect. ch : java.nio.channels.SocketChannel[connection-pending remote=localhost.localdomain/16.110.135.52:8020]; For more details see:  http://wiki.apache.org/hadoop/SocketTimeout
E0925 23:03:32.119706  9691 impala-server.cc:341] Aborting Impala Server startup due to improper configuration
E0925 23:22:09.366200 17027 Log4JLogger.java:115] Bundle "org.eclipse.jdt.core" requires "org.eclipse.core.resources" but it cannot be resolved.
E0925 23:22:09.366905 17027 Log4JLogger.java:115] Bundle "org.eclipse.jdt.core" requires "org.eclipse.core.runtime" but it cannot be resolved.
E0925 23:22:09.367164 17027 Log4JLogger.java:115] Bundle "org.eclipse.jdt.core" requires "org.eclipse.text" but it cannot be resolved.

 

3) [cloudera@localhost ~]$ impala-shell
Starting Impala Shell in unsecure mode
Error connecting: <class 'thrift.transport.TTransport.TTransportException'>, Could not connect to localhost.localdomain:21000
Unable to load history: [Errno 2] No such file or directory
Welcome to the Impala shell. Press TAB twice to see a list of available commands.

Copyright (c) 2012 Cloudera, Inc. All rights reserved.

(Shell build version: Impala Shell v1.1.1 (83d5868) built on Fri Aug 23 17:28:05 PDT 2013)
[Not connected] >

 

Help needed at the earliest.

 


 

 

 

1 REPLY 1

Re: Impala-Shell error

Master Collaborator

It appears that you are using the loopback (eg. 127.0.0.1) address for your bindings.  You should create an actual local hostname and attach that to your real IP address.  Loopback will not work for hadoop.

 

1) run the following: 

 

hostname

 

  and

 

ifconfig -a

 

2) you should probably have an actual IP address listed with your "eth0" network interface, and that IP address should be associated with your hostname in /etc/hosts (or DNS).  On a new Linux VM, you'll not get a hostname, so you may have to create one first with these instructions:

 

http://www.ghacks.net/2009/07/06/set-your-hostname-in-linux/

 

I think once you get your hostname/IP all configured properly, things may start to work.  But you also may need to check your Impala configs, because your error message is showing that it's trying to bind to port 21000, but it doesn't seem that the service is binding to that address.

 

HTH,


Clint

Don't have an account?
Coming from Hortonworks? Activate your account here