[
https://issues.apache.org/jira/browse/HBASE-24205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125532#comment-17125532
]
ramkrishna.s.vasudevan commented on HBASE-24205:
------------------------------------------------
bq.Aggregated at region level means it will consider all CFs/Stores under that
region. Say we have 2 store (CFs) under region and one having read pattern of
recent data and other not, the aggregated at region level will not be a real
insight.
Previously the patch had per store per region detail. The only thing was to
make use of it, we had to aggregate it at the consumer side.
Now that is also aggregated as region vs store - with a value.
So if we add all the region vs store metric value should be equal to table vs
store metric. (for that specific store).
> Create metric to know the number of reads that happens from memstore
> --------------------------------------------------------------------
>
> Key: HBASE-24205
> URL: https://issues.apache.org/jira/browse/HBASE-24205
> Project: HBase
> Issue Type: Improvement
> Components: metrics
> Affects Versions: 3.0.0-alpha-1
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
> Attachments: screenshot.png, screenshot_tablevscf.png
>
>
> A metric to identify number of reads that were served from memstore (atleast
> if the gets can be accounted for) then it gives a value addition to know if
> among the reads how much was targeted at the most recent data.
> Currently the existing metric framework at region level should be enough but
> we can also add a metric per store level. That will be more granular.
> We can also expose this via HbTop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
