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.

Error connecting: TTransportException, Could not connect to cm1home:21000

Error connecting: TTransportException, Could not connect to cm1home:21000

Rising Star

I have deployed CDH 5.2.x. all services are working fine. I am able to run mapreduce jobs. I can access hbase, hive, hue etc.

 

when I run impala-shell I get an error

 

Error connecting: TTransportException, Could not connect to cm1home:21000

 

 

1. I can do uname -a on all machines. 

 

I an do python -c 'import socket; print socket.getfqdn(),socket.gethostbyname(socket.getfqdn())' successfully on all machines

 

iptables is stopped and off on all machines.

 

in my cloudera manager console. I can see that my impala service is healthy. in the log file I do not see any errors ... but these are the last few lines

 

10:24:49.088 PMINFOinit.cc:136

Using hostname: cm1home

10:24:49.088 PMINFOlogging.cc:100

Flags (see also /varz are on debug webserver):
--catalog_service_port=26000
....

10:24:49.088 PMINFOwebserver.cc:154

Starting webserver on 0.0.0.0:25010

10:24:49.088 PMINFOwebserver.cc:168

Document root: /opt/cloudera/parcels/CDH-5.2.1-1.cdh5.2.1.p0.12/lib/impala

10:24:49.088 PMINFOwebserver.cc:234

Webserver started

10:24:49.141 PMINFOthrift-server.cc:387

ThriftServer 'StatestoreService' started on port: 24000

10:24:49.394 PMINFOstatestore.cc:314

Creating new topic: ''impala-request-queue' on behalf of subscriber: 'impalad@hd1home:22000

10:24:49.394 PMINFOstatestore.cc:314

Creating new topic: ''catalog-update' on behalf of subscriber: 'impalad@hd1home:22000

10:24:49.394 PMINFOstatestore.cc:314

Creating new topic: ''impala-membership' on behalf of subscriber: 'impalad@hd1home:22000

10:24:49.394 PMINFOstatestore.cc:321

Registering: impalad@hd1home:22000

10:24:49.396 PMINFOclient-cache.cc:107

CreateClient(): creating new client for hd1home:23000

10:24:49.396 PMINFOstatestore.cc:352

Subscriber 'impalad@hd1home:22000' registered (registration id: 8249428724f657e9:4bf0ac722e4c1e9d)

10:24:49.541 PMINFOstatestore.cc:321

Registering: impalad@hd2home:22000

10:24:49.542 PMINFOstatestore.cc:479

Preparing initial impala-membership topic update for impalad@hd2home:22000. Size = 100.00 B

10:24:49.542 PMINFOclient-cache.cc:107

CreateClient(): creating new client for hd2home:23000

10:24:49.548 PMINFOstatestore.cc:352

Subscriber 'impalad@hd2home:22000' registered (registration id: 3f4069d5f5910464:c9836fd7e24ca2b8)

10:24:49.902 PMINFOstatestore.cc:479

Preparing initial impala-membership topic update for impalad@hd1home:22000. Size = 100.00 B

10:24:50.131 PMINFOstatestore.cc:321

Registering: impalad@hd4home:22000

10:24:50.131 PMINFOstatestore.cc:479

Preparing initial impala-membership topic update for impalad@hd4home:22000. Size = 100.00 B

10:24:50.131 PMINFOclient-cache.cc:107

CreateClient(): creating new client for hd4home:23000

10:24:50.132 PMINFOstatestore.cc:352

Subscriber 'impalad@hd4home:22000' registered (registration id: bb46f6d07ad5482b:bec763db82f31c8e)

10:24:50.547 PMINFOstatestore.cc:479

Preparing initial impala-membership topic update for impalad@hd2home:22000. Size = 200.00 B

10:24:54.770 PMINFOstatestore.cc:321

Registering: impalad@hd3home:22000

10:24:54.774 PMINFOstatestore.cc:352

Subscriber 'impalad@hd3home:22000' registered (registration id: 834038f459d1cfe2:d18846305f34a4b6)

10:24:54.784 PMINFOstatestore.cc:479

Preparing initial impala-membership topic update for impalad@hd3home:22000. Size = 300.00 B

10:24:54.784 PMINFOclient-cache.cc:107

CreateClient(): creating new client for hd3home:23000

10:24:56.072 PMINFOstatestore.cc:321

Registering: catalog-server@cm1home:26000

10:24:56.072 PMINFOclient-cache.cc:107

CreateClient(): creating new client for cm1home:23020

10:24:56.072 PMINFOstatestore.cc:352

Subscriber 'catalog-server@cm1home:26000' registered (registration id: 2744bfbe34bc0106:ba0fbae77b48ca8e)

10:24:56.653 PMINFOstatestore.cc:479

Preparing initial catalog-update topic update for impalad@hd4home:22000. Size = 372.00 B

10:24:56.791 PMINFOstatestore.cc:479

Preparing initial catalog-update topic update for impalad@hd3home:22000. Size = 372.00 B

10:24:56.923 PMINFOstatestore.cc:479

Preparing initial catalog-update topic update for impalad@hd1home:22000. Size = 372.00 B

10:24:57.063 PMINFOstatestore.cc:479

Preparing initial catalog-update topic update for impalad@hd2home:22000. Size = 372.00 B

10:24:57.083 PMINFOstatestore.cc:479

Preparing initial catalog-update topic update for catalog-server@cm1home:26000. Size = 372.00 B

 

 

2 REPLIES 2
Highlighted

Re: Error connecting: TTransportException, Could not connect to cm1home:21000

Rising Star

From my 2nd machine in the cluster (hd1home) it connects fine 

 

[root@cm1home ~]# ssh hd1home
Last login: Sat Dec 20 22:14:43 2014 from abhishek-pc.home
[root@hd1home ~]# impala-shell
Starting Impala Shell without Kerberos authentication
Connected to hd1home:21000
Server version: impalad version 2.0.1-cdh5 RELEASE (build cc09df07d93c79351052eef2f4e5baf52373dc33)
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 v2.0.1-cdh5 (cc09df0) built on Wed Nov 19 10:57:34 PST 2014)
[hd1home:21000] >

 

So why doesn't this work on all machines in the cluster?

 

I thought this could be because the impala services are not running on cm1home. but when I try to do start services, on cm1home it says these services are not recognized

 

[root@cm1home ~]# sudo service impala-state-store start
impala-state-store: unrecognized service
[root@cm1home ~]# sudo service impala-server start
impala-server: unrecognized service
[root@cm1home ~]# sudo service impala-catalog start
impala-catalog: unrecognized service
[root@cm1home ~]#

 

Re: Error connecting: TTransportException, Could not connect to cm1home:21000

Contributor

I do have same issue, on Kerberos enalbed cluster Impala-shell works fine on one machine but gives the same TTransportException error on another machine of the cluster, can anybody please help on the same.

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