Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Common Ports of Components

Updated on 2024-11-29 GMT+08:00

Scenario

When you buy a custom cluster of an LTS version, you can customize the component port. If you do not want to customize a port, an open source port is used.

  • Open source: Find the default port of the component in the Default Open Source Port column of the following table.
  • Custom: Find the default port of the component in the Default Custom Port column of the following table.
  • If there is only the Default Port column, the open source port of the component is the same as the default custom port.

If the cluster is not of an LTS version, the Component Port parameter is unavailable and only an open source port can be used. For details, see the Default Open Source Port or Default Port column.

Common HBase Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

hbase.master.port

16000

21300

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

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

hbase.master.info.port

16010

21301

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

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

hbase.regionserver.port

16020

21302

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

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

hbase.regionserver.info.port

16030

21303

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

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

hbase.thrift.info.port

9095

21304

Thrift Server listening port of Thrift Server

This port is used for:

Listening when the client is connected

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

hbase.regionserver.thrift.port

9090

21305

Thrift Server listening port of RegionServer

This port is used for:

Listening when the client is connected to the RegionServer

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

hbase.rest.info.port

8085

21308

Port of the RegionServer RESTServer native web page

-

21309

21309

REST port of RegionServer RESTServer

Common HDFS Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

dfs.namenode.rpc.port

8020

25000

NameNode RPC port

This port is used for:

  1. Communication between the HDFS client and NameNode
  2. Connection between the DataNode and NameNode
    NOTE:

    The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

dfs.namenode.http.port

9870

25002

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
    NOTE:

    The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

dfs.namenode.https.port

9871

25003

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
    NOTE:

    The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

dfs.datanode.ipc.port

9867

25008

IPC server port of DataNode

This port is used for:

Connection between the client and DataNode to perform RPC operations.

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

dfs.datanode.port

9866

25009

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
    NOTE:

    The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

dfs.datanode.http.port

9864

25010

DataNode HTTP port

This port is used for:

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

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

dfs.datanode.https.port

9865

25011

HTTPS port of DataNode

This port is used for:

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

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

dfs.JournalNode.rpc.port

8485

25012

RPC port of JournalNode

This port is used for:

Client communication to access multiple types of information

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

dfs.journalnode.http.port

8480

25013

JournalNode HTTP port

This port is used for:

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

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

dfs.journalnode.https.port

8481

25014

HTTPS port of JournalNode

This port is used for:

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

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

httpfs.http.port

14000

25018

Listening port of the HttpFS HTTP server

This port is used for:

Connecting to the HttpFS from the remote REST API

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

Common HetuEngine Ports

The protocol type of the port in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

server.port (HSBroker)

29860

29860

Specifies the port number that HSBroker listens to.

server.port (HSConsole)

29880

29880

Specifies the port number that HSConsole listens to.

server.port (HSFabric)

29900

29900

Specifies the port number that HSFabric listens to, which is used for cross-domain connections

gateway.port

29902

29902

Specifies the port number that HSFabric listens to, which is used for JDBC connections

Common Hive Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

templeton.port

9111

21055

Port used for WebHCat to provide 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

21066

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

21088

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

Common Hue Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

HTTP_PORT

8888

21200

Port for Hue to provide HTTPS services

This port is used to provide web services in HTTPS mode, which can be changed.

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

Common Kafka Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

port

9092

21005

Port for a broker to receive data and obtain services

ssl.port

9093

21008

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

sasl.port

21007

21007

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

sasl-ssl.port

21009

21009

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

Common Loader Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Port

Port Description

LOADER_HTTPS_PORT

21351

This port is used to provide 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

Common MapReduce Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

mapreduce.jobhistory.webapp.port

19888

26012

Web HTTP port of the JobHistory server

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

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

mapreduce.jobhistory.port

10020

26013

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
    NOTE:

    The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

mapreduce.jobhistory.webapp.https.port

19890

26014

Web HTTPS port of the JobHistory server

This port is used to view the web page of the JobHistory server.

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

Common Spark Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

hive.server2.thrift.port

22550

22550

JDBC thrift port

This port is used for:

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

NOTE:

If hive.server2.thrift.port is occupied, an exception indicating that the port is occupied is reported.

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

spark.ui.port

4040

22950

Web UI port of JDBC

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

NOTE:

The system verifies the port configuration. If the port is invalid, the value of the port plus 1 is used till the calculated value is valid. (A maximum number of 16 attempts are allowed. The number of attempts is specified by spark.port.maxRetries.)

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

spark.history.ui.port

18080

22500

JobHistory Web UI port

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

NOTE:

The system verifies the port configuration. If the port is invalid, the value of the port plus 1 is used till the calculated value is valid. (A maximum number of 16 attempts are allowed. The number of attempts is specified by spark.port.maxRetries.)

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

Common Storm Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

nimbus.thrift.port

6627

29200

Port for Nimbus to provide thrift services

supervisor.slots.ports

6700,6701,6702,6703

29200-29499

Port for receiving service requests that are forwarded from other servers

logviewer.https.port

29248

29248

Port for LogViewer to provide HTTPS services

ui.https.port

29243

29243

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

Common Yarn Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

yarn.resourcemanager.webapp.port

8088

26000

Web HTTP port of the ResourceManager service

yarn.resourcemanager.webapp.https.port

8090

26001

Web HTTPS port of the ResourceManager service

This port is used to access the Resource Manager web applications in security mode.

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

yarn.nodemanager.webapp.port

8042

26006

NodeManager Web HTTP port

yarn.nodemanager.webapp.https.port

8044

26010

NodeManager Web HTTPS port

This port is used for:

Accessing the NodeManager web application in security mode

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

Common ZooKeeper Ports

The protocol type of all ports in the table is TCP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

clientPort

2181

24002

ZooKeeper client port

This port is used for:

Connection between the ZooKeeper client and server.

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

Common Kerberos Ports

The protocol type of all ports in the table is TCP and UDP.

Parameter

Default Port

Port Description

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.

NOTE:

The port ID is a recommended value and is specified based on the product. The port range is not restricted in the code.

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

Common OpenTSDB Ports

The protocol type of the port in the table is TCP.

Parameter

Default Port

Port Description

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

Common Tez Ports

The protocol type of the port in the table is TCP.

Parameter

Default Port

Port Description

tez.ui.port

28888

Web UI port of Tez

Common KafkaManager Ports

The protocol type of the port in the table is TCP.

Parameter

Default Port

Port Description

kafka_manager_port

9099

Web UI port of KafkaManager

Common Presto Ports

The protocol type of the port in the table is TCP.

Parameter

Default Port

Port Description

http-server.http.port

7520

HTTP port for Presto coordinator to provide services to external systems

http-server.https.port

7521

HTTPS port for Presto coordinator to provide services to external systems

http-server.http.port

7530

HTTP port for Presto worker to provide services to external systems

http-server.https.port

7531

HTTPS port for Presto worker to provide services to external systems

Common Flink Ports

The protocol type of the port in the table is TCP.

Parameter

Default Port

Port Description

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

Common ClickHouse Ports

The protocol type of the port in the table is TCP and HTTP.

Parameter

Default Open Source Port

Default Custom Port

Port Description

interserver_http_port

9009

9009

HTTP port for the communication between ClickHouse servers.

interserver_https_port

9010

9010

HTTPS port for the communication between ClickHouse servers.

http_port

8123

8123

Port for connecting to the ClickHouse server through HTTP.

https_port

8443

8443

Port for connecting to the ClickHouse server through HTTPS.

tcp_port

9000

9000

Port for connecting the client to the ClickHouse server through TCP.

tcp_port_secure

9440

9440

Port for connecting the client to the ClickHouse server through TCP SSL.

lb_tcp_port

21424

21424

TCP port listened by ClickHouseBalancer

lb_http_port

21425

21425

HTTP port listened by ClickHouseBalancer

lb_https_port

21426

21426

HTTPS port listened by ClickHouseBalancer

lb_tcp_secure_port

21428

21428

TCP SSL port listened by ClickHouseBalancer

Common Impala Ports

The protocol type of the port in the table is TCP.

Parameter

Default Port

Port Description

--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

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback