Back to Starrocks

SHOW FRONTENDS

docs/en/sql-reference/sql-statements/cluster-management/nodes_processes/SHOW_FRONTENDS.md

4.1.03.9 KB
Original Source

SHOW FRONTENDS

SHOW FRONTENDS views the information of all FE nodes in the cluster, including their IP addresses, ports, roles, and status.

:::tip

Only users with the SYSTEM-level OPERATE privilege or the cluster_admin role can perform this operation.

:::

Syntax

sql
SHOW FRONTENDS

Return

sql
+------+------------------------------+-----------+-------------+----------+-----------+---------+--------+-----------+------+-------+-------------------+---------------------+----------+--------+---------------------+---------------+
| Id   | Name                         | IP        | EditLogPort | HttpPort | QueryPort | RpcPort | Role   | ClusterId | Join | Alive | ReplayedJournalId | LastHeartbeat       | IsHelper | ErrMsg | StartTime           | Version       |
+------+------------------------------+-----------+-------------+----------+-----------+---------+--------+-----------+------+-------+-------------------+---------------------+----------+--------+---------------------+---------------+

The following table describes the parameters returned by this statement.

ParameterDescription
IdThe unique ID of the FE node.
NameThe name of the FE node in BDBJE (typically IP_EditLogPort_Timestamp).
IPThe IP address of the FE node.
EditLogPortThe port used for BDBJE communication (default: 9010).
HttpPortThe HTTP server port of the FE node (default: 8030). Used for accessing the FE web UI.
QueryPortThe MySQL protocol port (default: 9030). Used by MySQL clients to connect to StarRocks.
RpcPortThe Thrift server port (default: 9020). Used for internal RPC communication.
RoleThe role of the FE node. <ul><li>LEADER: The master node, handles metadata writes.</li><li>FOLLOWER: Participates in elections and metadata syncing.</li><li>OBSERVER: Syncs metadata but does not participate in elections.</li></ul>
ClusterIdThe unique ID of the cluster. All nodes in the same cluster must have the same ClusterId.
JoinWhether the node has joined the BDBJE group. <ul><li>true: Joined.</li><li>false: Not joined (note: a node might be removed but still show true temporarily).</li></ul>
AliveWhether the node is alive and responding. <ul><li>true: Alive.</li><li>false: Not alive.</li></ul>
ReplayedJournalIdThe maximum metadata journal ID that the node has currently replayed. Used to check if the node is in sync with the Leader.
LastHeartbeatThe timestamp of the last heartbeat received.
IsHelperWhether the node is a Helper node (specified during cluster startup to help other nodes join).
ErrMsgError message displayed if the heartbeat fails
StartTimeThe time when this FE process was started.
VersionThe StarRocks version running on this FE node.

Example

View the information of all FE nodes in the cluster.

Plain
mysql> SHOW FRONTENDS\G;
*************************** 1. row ***************************
               Id: 1
             Name: 127.0.0.1_9010_1766983864084
               IP: 127.0.0.1
      EditLogPort: 9010
         HttpPort: 8030
        QueryPort: 9030
          RpcPort: 9020
             Role: LEADER
        ClusterId: 391198626
             Join: true
            Alive: true
ReplayedJournalId: 59720
    LastHeartbeat: 2026-01-21 13:24:20
         IsHelper: true
           ErrMsg:
        StartTime: 2026-01-20 12:58:48
          Version: 4.0.2-1f1aa9c
1 row in set (0.01 sec)