hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17016) Reimplement per-region latency histogram metrics
Date Wed, 05 Apr 2017 18:37:42 GMT

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

Mikhail Antonov commented on HBASE-17016:
-----------------------------------------

Why are we moving things to 1.5 before 1.4 is getting to code freeze?

> 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.5.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.15#6346)

Mime
View raw message