[
https://issues.apache.org/jira/browse/HBASE-26721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-26721:
---------------------------------
Attachment: HBASE-26721 Screen Shot.png
> 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
> Priority: Major
> Attachments: HBASE-26721 Screen Shot.png
>
>
> 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)
