[
https://issues.apache.org/jira/browse/HBASE-15518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16250264#comment-16250264
]
Hudson commented on HBASE-15518:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4048 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/4048/])
HBASE-19244 Fix simple typos in HBASE-15518 descriptions (Clay B.) (tedyu: rev
3b8d95ad8b46ba9d71bb564bce624f6990b3e287)
* (edit)
hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsTableSource.java
> 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.3.0
>
> Attachments: HBASE-15518-v1.patch, HBASE-15518-v2.patch,
> HBASE-15518-v3.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.4.14#64029)
