You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2026/06/24 13:04:00 UTC
[jira] [Resolved] (HBASE-29289) Make hbase master ui & hbtop client view show cluster client connections info
[ https://issues.apache.org/jira/browse/HBASE-29289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wellington Chevreuil resolved HBASE-29289.
------------------------------------------
Resolution: Fixed
Merged to master, branch-3, branch-2 and branch-2.6. Thanks for the contribution, [~dev8103] !
> Make hbase master ui & hbtop client view 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
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.7
>
> 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.
> *Update* :
> We are using existing ClusterStatus.ClientMetrics, MetricsUserAggregateImpl, MetricsUserSourceImpl to periodically send these metrics from RegionServers to Master and render it in Master UI and hbtop client view, that way we don't need the extra tracking logic at related RPC layer classes as MetricsUserAggregateImpl already provides its own maps and tracking mechanism.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)