You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/04/01 05:24:00 UTC

[jira] [Commented] (HBASE-26545) Implement tracing of scan

    [ https://issues.apache.org/jira/browse/HBASE-26545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515714#comment-17515714 ] 

Hudson commented on HBASE-26545:
--------------------------------

Results for branch branch-2
	[build #504 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/504/]: (/) *{color:green}+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-2/504/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/504/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/504/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/504/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: 2.6.0, 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)