My Oracle Support Banner

Starting 'impala-shell' on Oracle BDA V3.0.1 Secure Client/Edge Server Raises "Error connecting: TTransportException" (Doc ID 1923360.1)

Last updated on NOVEMBER 06, 2019

Applies to:

Big Data Appliance Integrated Software - Version 3.0 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

  

 

On a CDH 5.0.1 secure client/edge server running 'impala-shell' V1.3.1-cdh5 to access an HDFS cluster on a V3.0.1/CDH 5.0.1 secure BDA cluster (e.g. Kerberos enabled) these errors are raised:

Error connecting: TTransportException, Could not connect to <clientname>.example.com:21000

and/or

Error connecting: TTransportException, Could not start SASL



The sequence leading to each is below.  The examples make "bdanodex" which represents the BDA node running the Impala Daemon being connected to and use the default Impala Daemon Frontend port of 21000.

Note: You can connect to any host in your cluster that is running the impalad daemon. If port 21000 is not correct for the environment use the port required. For example if you connect to an instance of impalad that was started with an alternate port specified by the --fe_port flag, provide that alternative port.  
 

1. For:  Error connecting: TTransportException, Could not connect to <bdaclient>.example.com:21000

  

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.