[
https://issues.apache.org/jira/browse/HBASE-15267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149851#comment-15149851
]
Anoop Sam John commented on HBASE-15267:
----------------------------------------
Ya for scan case there is an update call as shown above.
But in HRegion
{code}
public synchronized boolean next(List<Cell> outResults, ScannerContext
scannerContext)
throws IOException {
if (this.filterClosed) {
throw new UnknownScannerException("Scanner was closed (timed out?) " +
"after we renewed it. Could be caused by a very slow scanner " +
"or a lengthy garbage collection");
}
startRegionOperation(Operation.SCAN);
readRequestsCount.increment();
try {
return nextRaw(outResults, scannerContext);
} finally {
{code}
These same lines getting executed for read and scan.. Still some thing
missing!!
> Read requests count metric is increased when Get operation does not return
> any record
> -------------------------------------------------------------------------------------
>
> Key: HBASE-15267
> URL: https://issues.apache.org/jira/browse/HBASE-15267
> Project: HBase
> Issue Type: Bug
> Reporter: Eungsop Yoo
> Priority: Minor
> Attachments: HBASE-15267-v1.patch, HBASE-15267.patch
>
>
> Read requests count is increased when Get operation returns no record by
> filtering out. In such cases, Get for deleted record, Get for TTL expired
> record and Get for filtering out.
> So I fixed the bug and added some more test cases for read metrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
