[ https://issues.apache.org/jira/browse/HBASE-27687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Beaudreault resolved HBASE-27687. --------------------------------------- Fix Version/s: 2.6.0 3.0.0-beta-2 Release Note: Read size quotas are now evaluated against block bytes scanned for a request, rather than result size. Block bytes scanned is a measure of the total size in bytes of all hfile blocks opened to serve a request. This results in a much more accurate picture of actual work done by a query and is the recommended mode. One can revert to the old behavior by setting hbase.quota.use.result.size.bytes to true. Resolution: Fixed > Enhance quotas to consume blockBytesScanned rather than response size > --------------------------------------------------------------------- > > Key: HBASE-27687 > URL: https://issues.apache.org/jira/browse/HBASE-27687 > Project: HBase > Issue Type: Improvement > Reporter: Bryan Beaudreault > Assignee: Bryan Beaudreault > Priority: Major > Labels: pull-request-available > Fix For: 2.6.0, 3.0.0-beta-2 > > > As of HBASE-27558 we now apply quota.getReadAvailable() to max block bytes > scanned by scans/multis. This issue enhances further so that we can track > read size consumed in Quotas based on block bytes scanned rather than > response size. In this mode, quotas would end-to-end be based on > blockBytesScanned. > Right now we call quota.addGetResult or addScanResult. This would just be a > matter of no-oping those calls, and calling RpcCall.getBlockBytesScanned() in > Quota.close() instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)