List of Open Source Component Ports

hbase.master.port

16000

HMaster RPC port. This port is used to connect the HBase client to HMaster.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hbase.master.info.port

16010

HMaster HTTPS port. This port is used by the remote web client to connect to the HMaster UI.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hbase.regionserver.port

16020

RegoinServer (RS) RPC port. This port is used to connect the HBase client to RegionServer.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hbase.regionserver.info.port

16030

HTTPS port of the Region server. This port is used by the remote web client to connect to the RegionServer UI.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hbase.thrift.info.port

9095

Thrift Server listening port of Thrift Server.

This port is used for:

Listening when the client is connected

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hbase.regionserver.thrift.port

9090

Thrift Server listening port of RegionServer.

This port is used for:

Listening when the client is connected to the RegionServer

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hbase.rest.info.port

8085

Port of the RegionServer RESTServer native web page

-

21309

REST port of RegionServer RESTServer

dfs.namenode.rpc.port

• 9820 (versions earlier than MRS 3.x)
• 8020 (MRS 3.x and later)

NameNode RPC port.

This port is used for:

1. Communication between the HDFS client and NameNode

2. Connection between the DataNode and NameNode

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

dfs.namenode.http.port

9870

HDFS HTTP port (NameNode).

This port is used for:

1. Point-to-point NameNode checkpoint operations.

2. Connecting the remote web client to the NameNode UI

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

dfs.namenode.https.port

9871

HDFS HTTPS port (NameNode).

This port is used for:

1. Point-to-point NameNode checkpoint operations

2. Connecting the remote web client to the NameNode UI

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

dfs.datanode.ipc.port

9867

IPC server port of DataNode.

This port is used for:

Connection between the client and DataNode to perform RPC operations.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

dfs.datanode.port

9866

DataNode data transmission port.

This port is used for:

1. Transmitting data from HDFS client from or to the DataNode

2. Point-to-point DataNode data transmission

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

dfs.datanode.http.port

9864

DataNode HTTP port.

This port is used for:

Connecting to the DataNode from the remote web client in security mode

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

dfs.datanode.https.port

9865

HTTPS port of DataNode.

This port is used for:

Connecting to the DataNode from the remote web client in security mode

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

dfs.JournalNode.rpc.port

8485

RPC port of JournalNode.

This port is used for:

Client communication to access multiple types of information

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

dfs.journalnode.http.port

8480

JournalNode HTTP port

This port is used for:

Connecting to the JournalNode from the remote web client in security mode

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

dfs.journalnode.https.port

8481

HTTPS port of JournalNode.

This port is used for:

Connecting to the JournalNode from the remote web client in security mode

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

httpfs.http.port

14000

Listening port of the HttpFS HTTP server.

This port is used for:

Connecting to the HttpFS from the remote REST API

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

templeton.port

9111

Port used by WebHCat for providing the REST service.

This port is used for:

Communication between the WebHCat client and WebHCat server

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hive.server2.thrift.port

10000

Port for HiveServer to provide Thrift services.

This port is used for:

Communication between the HiveServer and HiveServer client

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hive.metastore.port

9083

Port for MetaStore to provide Thrift services.

This port is used for:

Communication between the MetaStore client and MetaStore, that is, communication between HiveServer and MetaStore.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hive.server2.webui.port

10002

Web UI port of Hive.

This port is used for: HTTPS/HTTP communication between Web requests and the Hive UI server

HTTP_PORT

8888

Port for Hue to provide HTTPS services.

This port is used for: providing web services in HTTPS mode (The port can be modified.)

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

port

9092

Port for a broker to receive data and obtain services

ssl.port

9093

SSL port used by a broker to receive data and obtain services

sasl.port

21007

SASL security authentication port provided by a broker, which provides the secure Kafka service

sasl-ssl.port

21009

Port used by a broker to provide encrypted service based on the SASL and SSL protocols

LOADER_HTTPS_PORT

21351

This port is used for: providing REST APIs for configuration and running of Loader jobs

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

-

8080

Port provided by WebService for user access.

This port is used to access the web UI over HTTP.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

-

28443

Port provided by WebService for user access.

This port is used to access the web UI over HTTPS.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

mapreduce.jobhistory.webapp.port

19888

Web HTTP port of the JobHistory server.

This port is used for: viewing the web page of the JobHistory server

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

mapreduce.jobhistory.port

10020

Port of the JobHistory server.

This port is used for:

1. Task data restoration in the MapReduce client

2. Obtaining task report in the Job client

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

mapreduce.jobhistory.webapp.https.port

19890

Web HTTPS port of the JobHistory server.

This port is used for: viewing the web page of the JobHistory server

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

hive.server2.thrift.port

22550

JDBC thrift port.

This port is used for:

Socket communication between Spark2.1.0 CLI/JDBC client and server

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

spark.ui.port

4040

Web UI port of JDBC

This port is used for: HTTPS/HTTP communication between Web requests and the JDBC Server Web UI server

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

spark.history.ui.port

18080

JobHistory Web UI port

This port is used for: HTTPS/HTTP communication between Web requests and Spark2.1.0 History Server

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

nimbus.thrift.port

6627

Port for Nimbus to provide thrift services

supervisor.slots.ports

6700,6701,6702,6703

Port for receiving service requests that are forwarded from other servers

logviewer.https.port

29248

Port for the LogViewer to provide HTTPS services

ui.https.port

29243

Port for the Storm UI to provide HTTPS services (ui.https.port)

yarn.resourcemanager.webapp.port

8088

Web HTTP port of the ResourceManager service.

yarn.resourcemanager.webapp.https.port

8090

Web HTTPS port of the ResourceManager service.

This port is used for: accessing the Resource Manager web applications in security mode

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

yarn.nodemanager.webapp.port

8042

NodeManager Web HTTP port

yarn.nodemanager.webapp.https.port

8044

NodeManager Web HTTPS port.

This port is used for:

Accessing the NodeManager web application in security mode

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

clientPort

2181

ZooKeeper client port.

This port is used for:

Connection between the ZooKeeper client and server.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

kdc_ports

21732

Kerberos server port.

This port is used for:

Performing Kerberos authentication for components This parameter may be used during the configuration of mutual trust between clusters.

• Is the port enabled by default during the installation: Yes
• Is the port enabled after security hardening: Yes

tsd.network.port

4242

Web UI port of OpenTSDB.

This port is used for: HTTPS/HTTP communication between web requests and the OpenTSDB UI server

tez.ui.port

28888

Web UI port of Tez

kafka_manager_port

9099

Web UI port of KafkaManager.

http-server.http.port

7520

HTTP port of Presto coordinator to provide services for external entities

http-server.https.port

7521

HTTPS port of Presto coordinator to provide services for external entities

http-server.http.port

7530

HTTP port used by Presto worker to provide services for external entities

http-server.https.port

7531

HTTPS port used by Presto worker to provide services for external entities

jobmanager.web.port

32261-32325

Web UI port of Flink.

This port is used for: HTTP/HTTPS communication between the client web requests and Flink server

tcp_port

9000

TCP port for accessing the service client.

http_port

8123

HTTP port for accessing the service client.

https_port

8443

HTTPS port for accessing the service client.

tcp_port_secure

9440

TCP With SSL port for accessing the service client. This port is enabled only in security mode by default.

--beeswax_port

21000

Port for impala-shell communication.

--hs2_port

21050

Port for Impala application communication.

--hs2_http_port

28000

Port used by Impala to provide the HiveServer2 protocol for external systems.