[
https://issues.apache.org/jira/browse/HBASE-28302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault resolved HBASE-28302.
---------------------------------------
Fix Version/s: 2.6.0
3.0.0-beta-2
Release Note: Adds a new getFsReadTime() to the slow log records, and
fsReadTime counter to ScanMetrics. In both cases, this is the cumulative time
spent reading blocks from hdfs for the given request. Additionally, a new
fsSlowReadsCount jmx metric is added to the sub=IO bean. This is the count of
HDFS reads which took longer than hbase.fs.reader.warn.time.ms.
Assignee: Bryan Beaudreault
Resolution: Fixed
Thanks [~ndimiduk] for the review! Pushed to master, branch-3, branch-2,
branch-2.6.
> Add tracking of fs read times in ScanMetrics and slow logs
> ----------------------------------------------------------
>
> Key: HBASE-28302
> URL: https://issues.apache.org/jira/browse/HBASE-28302
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Assignee: Bryan Beaudreault
> Priority: Major
> Fix For: 2.6.0, 3.0.0-beta-2
>
>
> We've had this in our production for a while, and it's useful info to have.
> We already track FS read times in
> [HFileBlock|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/HFileBlock.java#L1828-L1831C10].
> We can project that into the ScanMetrics instance and slow log pretty
> easily. It is also helpful to add a slow.fs.read.threshold, over which we log
> a warn
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
