[
https://issues.apache.org/jira/browse/HBASE-17017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15638116#comment-15638116
]
Enis Soztutar commented on HBASE-17017:
---------------------------------------
Thousands of counters are not that bad compared to millions at least. However
agreed that we can think about purging these all together. We now have
per-table metrics which should be the way to expose information, rather than
per-region.
In our deployments, we always disable per-region metrics because customers end
up with tens of thousands of regions in total, and there is no way to look at
per-region metrics without proper tooling. If you have more than 100 regions,
the information is not that useful unless again there is some good tooling
which most of the users would lack. FB was using per-region metrics, so we can
see whether they are fine with that.
> Remove the current per-region latency histogram metrics
> -------------------------------------------------------
>
> Key: HBASE-17017
> URL: https://issues.apache.org/jira/browse/HBASE-17017
> Project: HBase
> Issue Type: Sub-task
> Components: metrics
> Affects Versions: 2.0.0, 1.4.0
> Reporter: Duo Zhang
> Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.4.0
>
> Attachments: Screen Shot 2016-11-04 at 3.00.21 PM.png, Screen Shot
> 2016-11-04 at 3.38.42 PM.png, hbase-17017_v1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
