Ports Used by Impala

Impala uses the TCP ports listed in the following table. Before deploying Impala, ensure these ports are open on each system.

Component Service Port Access Requirement Comment

Impala Daemon

Impala Daemon Frontend Port

21000

External

Used to transmit commands and receive results by impala-shell and version 1.2 of the Cloudera ODBC driver.

Impala Daemon

Impala Daemon Frontend Port

21050

External

Used to transmit commands and receive results by applications, such as Business Intelligence tools, using JDBC, the Beeswax query editor in Hue, and version 2.0 or higher of the Cloudera ODBC driver.

Impala Daemon

Impala Daemon Backend Port

22000

Internal

Internal use only. Impala daemons use this port to communicate with each other.

Impala Daemon

StateStoreSubscriber Service Port

23000

Internal

Internal use only. Impala daemons listen on this port for updates from the statestore daemon.

Catalog Daemon

StateStoreSubscriber Service Port

23020

Internal

Internal use only. The catalog daemon listens on this port for updates from the statestore daemon.

Impala Daemon

Impala Daemon HTTP Server Port

25000

External

Impala web interface for administrators to monitor and troubleshoot.

Impala StateStore Daemon

StateStore HTTP Server Port

25010

External

StateStore web interface for administrators to monitor and troubleshoot.

Impala Catalog Daemon

Catalog HTTP Server Port

25020

External

Catalog service web interface for administrators to monitor and troubleshoot. New in Impala 1.2 and higher.

Impala StateStore Daemon

StateStore Service Port

24000

Internal

Internal use only. The statestore daemon listens on this port for registration/unregistration requests.

Impala Catalog Daemon

Catalog Service Port

26000

Internal

Internal use only. The catalog service uses this port to communicate with the Impala daemons. New in Impala 1.2 and higher.