All Products
Search
Document Center

E-MapReduce:UI and ports

Last Updated:Mar 26, 2026

This topic describes the default ports used by frontend (FE) and backend (BE) nodes in a StarRocks cluster on E-MapReduce (EMR), and explains how to access the FE UI and the BE metrics endpoint.

FE ports

Port name Default port Version Communication direction Description
http_port 8030 EMR V5.8.0 and earlier / EMR V3.42.0 and earlier FE <--> User HTTP server port on the FE
http_port 18030 EMR V5.9.0 and later / EMR V3.43.0 and later FE <--> User HTTP server port on the FE
rpc_port 9020 All versions BE --> FE; FE <--> FE Thrift server port on the FE
query_port 9030 All versions FE <--> User MySQL server port on the FE

Access the FE UI

Enter FE_IP:http_port in your browser's address bar to open the FE UI.

FE_IP is typically a public IP address.

BE ports

Port name Default port Version Communication direction Description
be_port 9060 All versions FE --> BE Thrift server port on the BE. Receives requests from an FE.
webserver_port 8040 EMR V5.8.0 and earlier / EMR V3.42.0 and earlier BE <--> BE HTTP server port on the BE
webserver_port 18040 EMR V5.9.0 and later / EMR V3.43.0 and later BE <--> BE HTTP server port on the BE
heartbeat_service_port 9050 All versions FE --> BE Heartbeat service port for the Thrift server on the BE. Receives heartbeat messages from an FE.
brpc_port 8060 All versions FE <--> BE; BE <--> BE better Remote Procedure Call (bRPC) port on the BE. Used for communication between BEs.

Access BE metrics

Run the following command to get metrics from a BE node:

curl http://be_ip:webserver_port/metrics
be_ip is typically an internal IP address.

FAQ

Why do I fail to access a StarRocks cluster by using port 8030 or port 8040?