You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Dev Hingu (Jira)" <ji...@apache.org> on 2026/06/15 07:09:00 UTC
[jira] [Commented] (HBASE-29289) Make hbase master ui show cluster client connections info
[ https://issues.apache.org/jira/browse/HBASE-29289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18089011#comment-18089011 ]
Dev Hingu commented on HBASE-29289:
-----------------------------------
As per the suggestion from [~wchevreuil], we have decided to use the existing metrics subsystem for tracking and reporting these info.
I used [ClientMetrics|https://github.com/apache/hbase/blob/f36a1cf3269264cd225b7820aee15da7cb0214ad/hbase-protocol-shaded/src/main/protobuf/server/ClusterStatus.proto#L203] from ClusterStatus.proto to include these new fields and used existing framework of MetricsUserAggregateImpl, MetricsUserSourceImpl to transfer these metrics periodically from RegionServers to Master.
I've already raised a PR with this logic and added these new fields into hbtop client view as well.
> Make hbase master ui show cluster client connections info
> ---------------------------------------------------------
>
> Key: HBASE-29289
> URL: https://issues.apache.org/jira/browse/HBASE-29289
> Project: HBase
> Issue Type: New Feature
> Components: UI
> Reporter: terrytlu
> Assignee: Dev Hingu
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2025-05-07-16-57-06-132.png, image-2025-05-07-16-58-48-523.png
>
>
> The hmaster page can display as follows, so that the cluster admin can easily get the client info such as username/version/ip/socketNum and so on, the socketNum is aggregated by the previous info columns.
> !image-2025-05-07-16-58-48-523.png|width=942,height=321!
>
> The technical proposal is as follows:
> !image-2025-05-07-16-57-06-132.png|width=599,height=417!
> When the client requests to establish a connection with the HRegionServer, the request header contains the client user/version information.
> HRegionServer will maintain a channel connection with the client, which is managed in NettyRpcServer. we can save the client attribute information of each Channel, and regularly collect statistics on the attributes of all channels.
> HRegionServer can report the information to HMaster through HMaster's RegionServerReport api.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)