[
https://issues.apache.org/jira/browse/HBASE-15518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207284#comment-15207284
]
Enis Soztutar commented on HBASE-15518:
---------------------------------------
Per-region does not help unless there are already existing tools for doing
aggregations at the table level from per-region level metrics.
Per-table+per-regionserver however, is very easily aggregated with out-of-box
tools like opentsdb, graphite, etc so that you can get a per-table aggregated
view across the cluster. And usually, per-region metrics is already disabled
because of the very large number of metrics being generated versus, per table
metrics is 10x-1000x less.
I agree that we should be careful in making sure that the metrics collection or
aggregation at the per-table level should not be in the hot path. Since we
already have per-region metrics, simply aggregating them at the wrapper layer
should be good enough that regular code path is not affected.
> Add Per-Table metrics back
> --------------------------
>
> Key: HBASE-15518
> URL: https://issues.apache.org/jira/browse/HBASE-15518
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Alicia Ying Shu
> Fix For: 2.0.0, 1.4.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
(v6.3.4#6332)
