You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2023/12/05 21:11:00 UTC
[jira] [Updated] (HBASE-27532) Add block bytes scanned metrics
[ https://issues.apache.org/jira/browse/HBASE-27532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Beaudreault updated HBASE-27532:
--------------------------------------
Fix Version/s: 2.6.0
3.0.0-beta-1
Release Note: Adds blockBytesScannedCount metrics for the regionserver, table, and operations in JMX. Adds a countOfBlockBytesScanned to ScanMetrics.
Resolution: Fixed
Status: Resolved (was: Patch Available)
Apparently, I forgot to close this. It was merged to master/branch-3/branch-2
> Add block bytes scanned metrics
> -------------------------------
>
> Key: HBASE-27532
> URL: https://issues.apache.org/jira/browse/HBASE-27532
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Assignee: Bryan Beaudreault
> Priority: Major
> Labels: patch-available
> Fix For: 2.6.0, 3.0.0-beta-1
>
>
> Initially in HBASE-14978, but more recently improved in HBASE-27558 and HBASE-27570, we now track the amount of block bytes scanned by read requests. Random read use-cases (which might read 1 small row from a 64kb block) and heavily filtered scans (which might scan many blocks in order to return a needle in a haystack row) can unknowingly cause RegionServers to do more work than a user expects. Now that we have block IO accounting, we should expose this to the user in the form of jmx metrics and ScanMetrics.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)