[
https://issues.apache.org/jira/browse/HBASE-26531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492594#comment-17492594
]
Nick Dimiduk commented on HBASE-26531:
--------------------------------------
As of HBASE-26521, coprocessor exec endpoints on both region server and master
generate spans matching the coprocessor exec method call:
{{hbase.pb.ClientService/ExecService}} and
{{hbase.pb.ClientService/ExecRegionServerService}}. While this is correct, it
may not be what we want. Instead, we could read the exec params and replace the
method package/name with that of the coprocessor.
Alternatively, we could keep the {{hbase.pb.ClientService/ExecService}} span
and add metadata that describes the coprocessor method. This could be a nested
span that looks like the {{ExecService}} span but with the coprocessor method
name, or it could be done through custom attributes.
[~taklwu], [~elserj], [~zhangduo] opinions?
> Trace coprocessor exec endpoints
> --------------------------------
>
> Key: HBASE-26531
> URL: https://issues.apache.org/jira/browse/HBASE-26531
> Project: HBase
> Issue Type: Sub-task
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
>
> Decide how to trace Coprocessor Exec endpoints. They either look like table
> operations OR generic RPC calls... I'm guessing the latter, but will give it
> some study.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
