Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.