[
https://issues.apache.org/jira/browse/HBASE-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210616#comment-16210616
]
Anoop Sam John commented on HBASE-19035:
----------------------------------------
Ya I was abt to ask this Q on other issue comments.. Even if CP do the work
and by pass the original work, the action (like write or read) will be done via
Region level APIs only. So any way the metric will get update.. Seems there is
inconsistency as per this bug report.
For eg: as reported in the mail thread for bypass support, a delete op might be
converted to a special put at preDelete and actual write been carried out there
and doing bypass on core flow. So this write is again done by calling put API
on the Region which is updating some metric.. So whether CP on its own should
update metric? I mean the core metric. That might be double update issue.
Sorry am not knowing this metric area well.. Pls correct if wrong
> Miss metrics when coprocessor use region scanner to read data
> -------------------------------------------------------------
>
> Key: HBASE-19035
> URL: https://issues.apache.org/jira/browse/HBASE-19035
> Project: HBase
> Issue Type: Bug
> Reporter: Guanghao Zhang
>
> Region interface is exposed to coprocessor. So coprocessor use getScanner to
> get a region scanner to read data. But the scan metrics was only updated in
> region server level. So we will miss some scan metrics for the read from
> coprocessor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
