[
https://issues.apache.org/jira/browse/HBASE-25723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331407#comment-17331407
]
Hudson commented on HBASE-25723:
--------------------------------
Results for branch master
[build #272 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/272/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/272/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/272/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/272/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 3. [see log for
details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/272//artifact/output-integration/hadoop-3.log].
(note that this means we didn't check the Hadoop 3 shaded client)
> Temporarily remove the trace support for RegionScanner.next
> -----------------------------------------------------------
>
> Key: HBASE-25723
> URL: https://issues.apache.org/jira/browse/HBASE-25723
> Project: HBase
> Issue Type: Sub-task
> Components: scan, tracing
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> Please see the test result in HBASE-25658, tracing RegionScanner.next could
> lead to a 6% performance downgrading even if we do not enable tracing.
> I think the problem here is that, a single scan rpc call could lead to a
> bunch of RegionScanner.next. So if trace is enabled, there will be much more
> performance impact as we need to store a bunch of spans(maybe this could be
> limited by some parameters?).
> Anyway, let's remove it for now to land the basic trace framework first. Can
> improve later.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
