You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/07/01 20:32:00 UTC
[jira] [Closed] (HBASE-20240) CLONE - Add Per-Table metrics back
[ https://issues.apache.org/jira/browse/HBASE-20240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell closed HBASE-20240.
---------------------------------------
> CLONE - Add Per-Table metrics back
> ----------------------------------
>
> Key: HBASE-20240
> URL: https://issues.apache.org/jira/browse/HBASE-20240
> Project: HBase
> Issue Type: Sub-task
> Reporter: Xu Zhidan
> Assignee: Alicia Ying Shu
> Priority: Major
> Fix For: 1.3.0, 2.0.0
>
>
> We used to have per-table metrics, but it was removed in some restructuring. We have per-region metrics, and per-regionserver metrics, but nothing in between.
> For majority of users, per-region is too granular, they are mostly interested in table level aggregates. This is especially useful in multi-tenant cases where a table's disk usage, number of requests, etc can be made much more visible.
> In this jira, we'll add the basic infrastructure to add a single (or a few) per-table metrics. Than we can improve on that by adding remaining metrics from the region server level.
> The plan is to NOT aggregate per-table metrics at master for now. Just aggregation of per-region metrics at the per-table level for every regionserver.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)