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

ramkrishna.s.vasudevan commented on HBASE-24205:
------------------------------------------------

bq.Will make it awkward summing by table
Summing per region and per table is bit awkward like we need to group them 
using a map. Rest of the metrics is just summations. This is ok I believe 
considering the simplicity of the patch. 

bq.The name will be long (smile).
Its like making 'something already long longer' (smile). It will just add the 
Store_<storename>.

But I think we need to do that or we should be giving the details per region 
per store under an Mbean only. 

> 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)

Reply via email to