You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2016/11/04 01:53:58 UTC

[jira] [Commented] (HBASE-17016) Reimplement per-region latency histogram metrics

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

Duo Zhang commented on HBASE-17016:
-----------------------------------

Done.

> Reimplement per-region latency histogram metrics
> ------------------------------------------------
>
>                 Key: HBASE-17016
>                 URL: https://issues.apache.org/jira/browse/HBASE-17016
>             Project: HBase
>          Issue Type: Task
>          Components: metrics
>    Affects Versions: 2.0.0, 1.4.0
>            Reporter: Andrew Purtell
>             Fix For: 2.0.0, 1.4.0
>
>
> Follow up from HBASE-10656, where [~enis] says:
> {quote}
> the main problem is that we have A LOT of per-region metrics that are latency histograms. These latency histograms create many many Counter / LongAdder objects. We should get rid of per-region latencies and maybe look at reducing the per-region metric overhead.
> {quote}
> And [~ghelmling] gives us a good candidate to implement pre-region latency histograms [HdrHistogram|https://github.com/HdrHistogram/HdrHistogram].
> Let's consider removing the per-region latency histograms and reimplement using HdrHistogram.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)