You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Alicia Ying Shu (JIRA)" <ji...@apache.org> on 2016/04/05 02:20:25 UTC

[jira] [Commented] (HBASE-15518) Add Per-Table metrics back

    [ https://issues.apache.org/jira/browse/HBASE-15518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225368#comment-15225368 ] 

Alicia Ying Shu commented on HBASE-15518:
-----------------------------------------

Uploaded a patch for table level stats. It implemented the flow to get and publish the table level stats. Currently it includes three metrics to display besides the number of tables that are being tracked: numReadRequestsCount, numWriteRequestsCount and numTotalRequestsCount. 

> 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
>
>         Attachments: HBASE-15518.patch
>
>
> 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)