You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2021/12/07 00:12: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=17454301#comment-17454301 ] 

Nick Dimiduk commented on HBASE-26545:
--------------------------------------

Do the best of my knowledge, this type of thing isn't covered in any of the OpenTelemetry documentation/guidance/conventions. I've started a question thread over on their Slack, https://cloud-native.slack.com/archives/C01QZFGMLQ7/p1638556336052800.

> 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
>            Priority: Major
>
> 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)