[
https://issues.apache.org/jira/browse/HBASE-27888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733792#comment-17733792
]
Hudson commented on HBASE-27888:
--------------------------------
Results for branch branch-3
[build #5 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/5/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/5/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/5//console].
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/5/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Record readBlock message in log when it takes too long time
> -----------------------------------------------------------
>
> Key: HBASE-27888
> URL: https://issues.apache.org/jira/browse/HBASE-27888
> Project: HBase
> Issue Type: Improvement
> Components: HFile
> Affects Versions: 2.5.3
> Reporter: chaijunjie
> Assignee: chaijunjie
> Priority: Minor
> Fix For: 2.6.0, 2.5.6, 3.0.0-beta-1
>
>
> After HBASE-15160， we can record the readBlock message by TRACE log in
> org.apache.hadoop.hbase.io.hfile.HFileBlock.FSReaderImpl#readBlockDataInternal，
> But it record all read block message in TRACE log， some times， we only focus
> the block read cost too much time..
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
