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

Posted to dev@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2022/01/28 23:10:00 UTC

[jira] [Created] (HBASE-26721) Traces of async chains result in arbitrarily deep trace stack

Nick Dimiduk created HBASE-26721:
------------------------------------

             Summary: Traces of async chains result in arbitrarily deep trace stack
                 Key: HBASE-26721
                 URL: https://issues.apache.org/jira/browse/HBASE-26721
             Project: HBase
          Issue Type: Sub-task
          Components: tracing
    Affects Versions: 3.0.0-alpha-2
            Reporter: Nick Dimiduk


Trying out the latest {{master}} on a real cluster, traces of async operations do not report the way I expect. Actions that are sequential (for example, locate meta then locate region) do not render as trace peers. Instead the subsequent action is a child of the previous. I believe this means that we are not handling parent span context propagation in async callback chains. I've not yet tried branch-2 to see if it's applicable there as well.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)