[
https://issues.apache.org/jira/browse/HBASE-26545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514292#comment-17514292
]
Hudson commented on HBASE-26545:
--------------------------------
Results for branch master
[build #552 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/552/]:
(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/master/552/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/552/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/552/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}
> Implement tracing of scan
> -------------------------
>
> Key: HBASE-26545
> URL: https://issues.apache.org/jira/browse/HBASE-26545
> Project: HBase
> Issue Type: Sub-task
> Components: tracing
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
> Fix For: 3.0.0-alpha-3
>
>
> Naive tracing of a long scan, where each back-and-forth between client and
> server gets its own Span, can result in many 100's or 1000's of Spans. This
> is easily overwhelming for tracing infrastructure. Identify some solution
> that allows for a reasonable out-of-the-box behavior when a scan is to be
> traced.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
