[
https://issues.apache.org/jira/browse/HBASE-24205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119662#comment-17119662
]
ramkrishna.s.vasudevan edited comment on HBASE-24205 at 5/29/20, 2:29 PM:
--------------------------------------------------------------------------
{quote}Namespace_default_table_TestTable_store_info0_metric_readRequestCountOnMemstore"
{quote}
The parts of this metric are
NameSpace_<Namespacename>_table<tablename>_store<storename>_metric_<metricName>
was (Author: ram_krish):
bq.Namespace_default_table_TestTable_store_info0_metric_readRequestCountOnMemstore"
The parts of this metric are
NameSpace_<Namespace name>_table<tablename>_store<storename>_metric_<metricName>
> 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)