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 2022/04/28 12:20:00 UTC
[jira] [Updated] (HBASE-26648) Improve fidelity of RegionLocator spans
[ https://issues.apache.org/jira/browse/HBASE-26648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-26648:
---------------------------------
Status: Patch Available (was: In Progress)
> Improve fidelity of RegionLocator spans
> ---------------------------------------
>
> Key: HBASE-26648
> URL: https://issues.apache.org/jira/browse/HBASE-26648
> Project: HBase
> Issue Type: Sub-task
> Components: tracing
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
>
> While backporting HBASE-26474 to branch-2, I realized that the nuance of tracing of region locator calls is lacking. In the current implementation, all calls to the region locator produce {{SpanKind.CLIENT}} spans. This is correct only for the code path where the client reaches out to a remote host to populate cache locations. This doesn't happen every time.
> Instead, the top-level span should be {{SpanKind.INTERNAL}} and only when a region location must be requested remotely should we create a child span with {{SpanKind.CLIENT}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)