Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-26419 Tracing Spans of RPCs should follow otel semantic conventions
  3. HBASE-26721

Traces of async chains result in arbitrarily deep trace stack

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Cannot Reproduce
    • 3.0.0-alpha-2
    • None
    • tracing
    • None

    Description

      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.

      Attachments

        1. HBASE-26721 Screen Shot.png
          182 kB
          Nick Dimiduk

        Activity

          People

            Unassigned Unassigned
            ndimiduk Nick Dimiduk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: