[
https://issues.apache.org/jira/browse/HBASE-26648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531755#comment-17531755
]
Hudson commented on HBASE-26648:
--------------------------------
Results for branch branch-2.5
[build #111 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/111/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/111/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/111/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/111/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/111/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
> Fix For: 2.5.0, 3.0.0-alpha-3
>
>
> 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)
