Configuring Ports

Make sure the appropriate ports are open before you install ODP.

Tables in this section specify which ports must be opened for an ecosystem component or service to communicate with other components and services.

HBase Service Ports

Note the default ports used by various HBase services.

The following table lists the default ports used by the various HBase services.

Table 1: HBase Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

HMaster

Master Nodes (HBase Master Node and any back- up HBase Master node)

16000

TCP

The port used by HBase client to connect to the HBase Master.

Yes

hbase.master.port

HMaster Info Web UI

Master Nodes (HBase master Node and back up HBase Master node if any)

16010

HTTP

The port for the HBaseMaster web UI. Set to -1 if you do not want the info server to run.

Yes

hbase.master.info.port

RegionServer

All Slave Nodes

16020

TCP

The port used by HBase client to connect to the HBase RegionServer.

Yes (Typically admins, dev/support teams)

hbase.regionserver.port

RegionServer

All Slave Nodes

16030

HTTP

The port used by HBase client to connect to the HBase RegionServer.

Yes (Typically admins, dev/support teams)

hbase.regionserver.info.port

HBase REST Server (optional)

All REST Servers

8080

HTTP

The port used by HBase Rest Servers. REST servers are optional, and not installed by default

Yes

hbase.rest.port

HBase REST Server Web UI (optional)

All REST Servers

8085

HTTP

The port used by HBase Rest Servers web UI. REST servers are optional, and not installed by default

Yes (Typically admins, dev/support teams)

hbase.rest.info.port

HBase Thrift Server (optional)

All Thrift Servers

9090

TCP

The port used by HBase Thrift Servers. Thrift servers are optional, and not installed by default

Yes

N/A

HBase Thrift Server Web UI (optional)

All Thrift Servers

9095

TCP

The port used by HBase Thrift Servers web UI. Thrift servers are optional, and not installed by default

Yes (Typically admins, dev/support teams)

hbase.thrift.info.port

HDFS Service Ports

Note the default ports used by various HDFS services.

The following table lists the default ports used by the various HDFS services. (Note: Neither of these services are used in a standard ODP installation.)

Table 2: HDFS Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

NameNode WebUI

Master Nodes (NameNode and any back-up NameNodes)

50070

http

Web UI to look at current status of HDFS, explore file system

Yes (Typically admins, Dev/ Support teams, as well as extra- cluster users who require webhdfs/ hftp access, for example, to use distcp)

dfs.http.address



50470

https

Secure http service


dfs.https.address

NameNode metadata service


8020/ 9000

IPC

File system metadata operations

Yes (All clients who directly need to interact with the HDFS)

Embedded in URI specified by fs.defaultFS

DataNode

All Slave Nodes

50075

http

DataNode WebUI to access the status, logs, etc, and file data operations when using webhdfs or hftp

Yes (Typically admins, Dev/ Support teams, as well as extra- cluster users who require webhdfs/ hftp access, for example, to use distcp)

dfs.datanode.http.address



50475

https

Secure http service


dfs.datanode.https.address



50010 SASL based IPC (non- privilege port)

IPC

Secure data transfer


dfs.datanode.address



1019 Privilege IPC port

IPC

Secure data transfer


dfs.datanode.address



50020

IPC

Metadata operations

No

dfs.datanode.ipc.address



1022

https

Customer HTTP port for Secure DataNode deployment

Yes

dfs.datanode.http.address

Secondary NameNode

Secondary NameNode and any backup Secondary NameNode

50090

http

Checkpoint for NameNode metadata

No

dfs.secondary.http.address

ZooKeeper Failover Controller (ZKFC)


8019

IPC

RPC port for Zookeeper Failover Controller

No

dfs.ha.zkfc.port

Hive service ports

Note the default ports used by various Hive services.

The following table lists the default ports used by the various Hive services. (Note: Neither of these services are used in a standard ODP installation.)

Table 3: Hive Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

Hive Server

Hive Server machine (Usually a utility machine)

10000

tcp or http

Service for programatically (Thrift/ JDBC) connecting to Hive

Yes(Clients who need to connect to Hive either programatically or through UI SQL tools that use JDBC)

ENV Variable HIVE_PORT

Hive Web UI

Hive Server machine (Usually utility machine)

9999

http

Web UI to explore Hive schemas

Yes

hive.hwi.listen.port

Hive Metastore


9083

http


Yes (Clients that run Hive, Pig and potentially M/R jobs that use HCatalog)

hive.metastore.uris

Hue service port

Note the default port used by the Hue web listener.

The following table lists the default port used by the Hue web listener.

Service

Servers

Default Port Used

Protocol

Description

Need End User Access?

Configuration Parameters

Hue

Node that is running Hue

8888

http

Port used by the Hue web listener to server web pages for Hue

Yes

http_port property in the /etc/hue/ conf/hue.ini file

Kafka Service Ports

Note the default port used by Kafka.

The following table lists the default ports used by Kafka.

Table 4: Kafka Service Ports


Service

Servers

Default Port

Default Ambari Port

Protocol

Description

Need End User Access?

Kafka

Kafka Server

9092

6667

TCP

The port for Kafka server.



Kerberos Service Ports

Note the default port used by the designated Kerberos KDC.

The following table lists the default port used by the designated Kerberos KDC.

Table 5: Kerberos Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

KDC

Kerberos KDC server

88


Port used by the designated KDC



Knox Service Ports

Note the default port used by Knox.

The following table lists the default port used by Knox.

Table 6: Knox Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

Knox

Knox server

8443


Port used by Knox



MapReduce Service Ports

Note the default port used by the various MapReduce services.

The following table lists the default ports used by the various MapReduce services.

Table 7: MapReduce Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

MapReduce


10020

http

MapReduce JobHistory server address


mapreduce.jobhistory.address

MapReduce


19888

http

MapReduce JobHistory webapp address


mapreduce.jobhistory.webapp.address

MapReduce


13562

http

MapReduce Shuffle Port


mapreduce.shuffle.port

MapReduce


19890

https

MapReduce JobHistory webapp HTTPS address


mapreduce.jobhistory.webapp.https.address

MySQL Service Ports

Note the default ports used by the various MySQL services.

The following table lists the default ports used by the various MySQL services.

Table 8: MySQL Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

MySQL

MySQL database server

3306





Oozie Service Ports

Note the default ports used by Oozie.

The following table lists the default ports used by Oozie.

Table 9: Oozie Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

Oozie

Oozie Server

11000

TCP

The port Oozie server runs.

Yes

OOZIE_HTTP_PORT in oozie_env.sh

Oozie

Oozie Server

11001

TCP

The admin port Oozie server runs.

No

OOZIE_ADMIN_PORT in oozie_env.sh

Oozie

Oozie Server

11443

TCP

The port Oozie server runs when using HTTPS.

Yes

OOZIE_HTTPS_PORT in oozie_env.sh

Ozone Service Ports

Note the default ports used by Ozone.

The following table lists the default ports used by Ozone:

Service

Port

Configuration Key

Protocol

Description

Ozone Manager

9862

ozone.om.rpc-port

Hadoop RPC

RPC endpoint for clients and applications


9872

ozone.om.ratis-port

GRPC

RPC endpoint for OM HA instances to form a RAFT consensus ring


9874

ozone.om.http-port

HTTP

Ozone Manager Web UI


9875

ozone.om.https-port

HTTPS

Ozone Manager Web UI

Storage Container Manager (SCM)

9861

ozone.scm.datanode.port

Hadoop RPC

Port used by DataNodes to communicate with the SCM


9863

ozone.scm.block.client.port

Hadoop RPC

Port used by the Ozone Manager to communicate with the SCM for block related operations


9860

ozone.scm.client.port

Hadoop RPC

Port used by Ozone Manager and other clients to communicate with the SCM for container operations


9876

ozone.scm.http-port

HTTP

SCM Web UI


9877

ozone.scm.https-port

HTTPS

SCM Web UI

DataNode (DN)

9882

ozone.datanode.http-address

HTTP

DataNode Web UI


9883

ozone.datanode.https-address

HTTPS

DataNode Web UI


9858

dfs.container.ratis.ipc

GRPC

RAFT server endpoint that is used by clients and other DataNodes to replicate RAFT transactions and write data.


9859

dfs.container.ipc

GRPC

Endpoint that is used by clients and other DataNodes to read block data.


19864

hdds.datanode.client.address

RPC

Ozone DataNode client service address.

S3 Gateway (S3G)

9878

ozone.s3g.http-address

HTTP

S3 API REST Endpoint and Web UI


9879

ozone.s3g.https-address

HTTPS

S3 API REST Endpoint and Web UI

Recon Service

9891

ozone.recon.rpc-port

Hadoop RPC

Port used by Datanodes to communicate with Recon Server (reporting)


9898

ozone.recon.http-port

HTTP

Recon service Web UI and REST API


9899

ozone.recon.https-port

HTTPS

Recon service Web UI and REST API

Ranger Service Ports

Note the default ports used by Ranger.

The following table lists the default ports used by Ranger.

Table 10: Ranger Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

Ranger Admin

Ranger Admin Nodes

6080

HTTP

Port for Ranger Admin web UI.

Yes

ranger.service.http.port (in ranger-admin-site.xml)

Ranger Admin

Ranger Admin Nodes

6182

HTTPS

Port for Ranger Admin web UI (with SSL).

Yes

ranger.service.https.port (in ranger-admin- site.xml)

UNIX Auth Service

Ranger Usersync Node

5151

SSL/TCP

Port for UNIX Auth service.

No

ranger.usersync.port (in ranger-ugsync-site.xml)

Ranger KMS

Ranger KMS Nodes

9292

HTTP

Port for Ranger KMS.

No

ranger.service.http.port (in kms-site.xml)

Ranger KMS

Ranger KMS Nodes

9293

HTTPS

Port for Ranger KMS.

No

ranger.service.https.port(in kms-site.xml)

Solr used by Ranger

Solr

6083,6183

HTTP

Ports for auditing to Solr.

Yes

ranger-admin and all plug-ins

Sqoop Service Ports

Note the default ports used by Sqoop.

The following table lists the default ports used by Sqoop.

Table 11: Sqoop Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

Sqoop

Metastore

16000

TCP

Connection between Sqoop and the metastore

No

sqoop.metastore.server.port

Sqoop

JDBC Listener

Varies, depends on target database. For example, if moving data from MySQL, TCP port 3306 must be open.

TCP

Outbound port from the Hadoop cluster to the database. Varies depending on Database

No


Tez Ports

Note the default ports used by the various Tez services.

The following table lists the default ports used by the various Tez services.

Table 12: Tez Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

Tez AM, Tez Service


12999


Port to use for AMPoolService status

Yes (Clients who need to submit Hive queries or jobs to Tez AM or Tez Service) Yes

tez.ampool.ws.port



10030

http

Address on which to run the ClientRMProtocol proxy


tez.ampool.address

YARN Service Ports

Note the default ports used by the various YARN services.

The following table lists the default ports used by the various YARN services.

Table 13: YARN Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

Resource Manager WebUI

Master Nodes (Resource Manager and any back-up Resource Manager node)

8088

http

Web UI for Resource Manager

Yes

yarn.resourcemanager.webapp.address

Resource Manager Hostname

Master Nodes (Resource Manager Node)

8090

https

Resource Manager HTTPS Address

Yes

yarn.resourcemanager.webapp.https.address

Resource Manager

Master Nodes (Resource Manager Node)

8050

IPC

For application submissions

Yes (All clients who need to submit the YARN applications including Hive, Hive server, Pig)

Embedded in URI specified by yarn.resourcemanager.address

Resource Manager

Master Nodes (Resource Manager Node)

8025

http

For application submissions

Yes (All clients who need to submit the YARN applications including Hive, Hive server, Pig)

yarn.resourcemanager.resource-tracker.address

Scheduler

Master Nodes (Resource Manager Node)

8030

http

Scheduler Address

Yes (Typically admins, Dev/ Support teams)

yarn.resourcemanager.scheduler.address

Resource Manager

Master Nodes (Resource Manager Node)

8141

http

Scheduler Address

Yes (Typically admins, Dev/ Support teams)

yarn.resourcemanager.admin.address

NodeManager

Slave Nodes running NodeManager

45454

http

NodeManager Address

Yes (Typically admins, Dev/ Support teams)

yarn.nodemanager.address

NodeManager

Slave Nodes running NodeManager

8042

http

NodeManager Webapp Address

Yes (Typically admins, Dev/ Support teams)

yarn.nodemanager.webapp.address

Timeline Server

Master Nodes

10200

http

Timeline Server Address

Yes (Typically admins, Dev/ Support teams)

yarn.timeline-service.address

Timeline Server

Master Nodes

8188

http

Timeline Server Webapp Address

Yes (Typically admins, Dev/ Support teams)

yarn.timeline-service.webapp.address

Timeline Server

Master Nodes

8190

https

Timeline Server Webapp https Address

Yes (Typically admins, Dev/ Support teams)

yarn.timeline-service.webapp.https.address

Job History Service

Master Nodes

19888

https

Job History Service

Yes (Typically admins, Dev/ Support teams)

yarn.log.server.url

ZooKeeper Service Ports

Note the default ports used by Zookeeper service.

Table 14: ZooKeeper Service Ports

Service

Servers

Default Ports Used

Protocol

Description

Need End User Access?

Configuration Parameters

ZooKeeper Server

All ZooKeeper Nodes

2888

N/A

Port used by ZooKeeper peers to talk to each other.

No

X in server.N =host:X:Y

ZooKeeper Server

All ZooKeeper Nodes

3888

N/A

Port used by ZooKeeper peers to talk to each other.

No

X in server.N =host:X:Y

ZooKeeper Server

All ZooKeeper Nodes

2181

N/A

Property from ZooKeeper's config zoo.cfg. The port at which the clients connect.

Yes

X in server.N =host:X:Y


  Last updated