[
https://issues.apache.org/jira/browse/HBASE-17016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-17016:
------------------------------
Description:
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 his
Let's consider removing the per-region latency histograms until we have a low
impact (in time and space) accounting.
was:
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}
Let's consider removing the per-region latency histograms until we have a low
impact (in time and space) accounting.
> Reimplement per-region latency histogram metrics
> ------------------------------------------------
>
> Key: HBASE-17016
> URL: https://issues.apache.org/jira/browse/HBASE-17016
> Project: HBase
> Issue Type: Task
> 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 his
> Let's consider removing the per-region latency histograms until we have a low
> impact (in time and space) accounting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
