[
https://issues.apache.org/jira/browse/HBASE-27681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695183#comment-17695183
]
tianhang tang commented on HBASE-27681:
---------------------------------------
[~bbeaudreault] Thank you for so quick reply~~
{quote}
We should just add a release note
{quote}
Sorry I'm not sure how should I do, would you please give me some infos or an
example? Thank you.
{quote}
rename TableLatencies to TableRequests
{quote}
Agree... I merged table query meter(which is for QPS rate) and table latencies
metrics together. That's because the previous code does this, but of course QPS
is not latency, and there is also scanSize histogram in latency metrics. So I
don't think the name is suitable. Let me change it.
> Refactor Table Latency Metrics
> ------------------------------
>
> Key: HBASE-27681
> URL: https://issues.apache.org/jira/browse/HBASE-27681
> Project: HBase
> Issue Type: Improvement
> Reporter: tianhang tang
> Assignee: tianhang tang
> Priority: Major
> Attachments: image-2023-03-01-23-55-14-095.png,
> image-2023-03-01-23-56-16-819.png
>
>
> Benefit:
> # Table Latency Metrics could removed after table has been moved away. Fix
> HBASE-27617
> # Could remove the hash lookup caused by metrics map from the hot request
> path.
> # Reduce the output in jmx. As if we use jmx_exporter to collect metrics to
> Prometheus, the operation overhead of performing regular matching in metric
> is relatively high(especially region metrics, which might be next step).
> # I think that could be the first step after hbase-metrics released. It
> seems that the roadmap indicates that we should replace directly use
> hadoop-metrics2 with hbase-metrics.
> Influence:
> # The metrics structure in jmx will change.
> Old:
> !image-2023-03-01-23-55-14-095.png|width=450,height=407!
> New:
> !image-2023-03-01-23-56-16-819.png|width=615,height=479!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
