Database Reference
In-Depth Information
machine. The connection can not be established. You will see a connection error as
shown in following screenshot:
To troubleshoot the preceding connection problem, you can try the following options:
• Check if the hostname is correct and a connection between both machines is
working. You can use
ping
or another similar utility to check the connectivity
between machines.
• Make sure that the machine where the Impala shell is running can resolve the
Impala hostname, and the default port 21000 (or the other configured port) is
open for connectivity.
• Make sure that the firewall configuration is not blocking the connection.
• Check whether the respective process is running on the Impala daemon host
machine. You can use Cloudera Manager or the
ps
command to get more
information about the Impala process.
ODBC/JDBC-specific connectivity issues
Impala provides connection through the third-party application that uses the ODBC/
JDBC driver running on the machine, which is trying to connect to the Impala server.
The connection may not work due to various reasons, which are given as follows:
• ODBC use the default 21000 port and JDBC uses the 21050 port in Impala
to provide the connectivity; make sure that the incoming to these ports are
working. Cloudera ODBC connection 2.0 and 2.5 uses the 21050 port when
connecting to Impala.
• If your Impala cluster environment is secured through Kerberos or another
security mechanism, use appropriate settings in the ODBC/JDBC configura-
tion. In some cases, you may need to contact the application vendor to re-
ceive information about the problem.
• After the connection, you may find that some of the functions are not working
over the ODBC/JDBC connection. It is very much possible that not all func-
