You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/06/02 22:43:00 UTC
[jira] [Commented] (HBASE-24205) Create metric to know the number
of reads that happens from memstore
[ https://issues.apache.org/jira/browse/HBASE-24205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124446#comment-17124446 ]
Michael Stack commented on HBASE-24205:
---------------------------------------
I can see value in how many reads come from memstore vs files.
Can you say more about what read counts we currently do? We do it on a Region basis. You'd here add counting per Store which I could see of use. Would like to see how new metrics relate to the old counters (for example, in PR, seems like the Store counting might not agee w/ how Region counts are done -- e.g. null Gets are counting in one case but not in the other). Then I wonder if these Store-based accounts lose value if they are summed at the Table level dropping their Region context. Thanks Ram.
> 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)