[
https://issues.apache.org/jira/browse/KUDU-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864725#comment-16864725
]
Grant Henke commented on KUDU-2835:
-----------------------------------
Another related Jira for this is KUDU-351. Adding a session descriptor could
allow for differentiation between work even when the client is shared or
reused.
> Add custom id in RpcHeader
> --------------------------
>
> Key: KUDU-2835
> URL: https://issues.apache.org/jira/browse/KUDU-2835
> Project: Kudu
> Issue Type: Improvement
> Reporter: Xu Yao
> Assignee: Xu Yao
> Priority: Major
>
> In our production environment, there are many distributed jobs that send
> request to Kudu by KuduClient. However, if there are some RPC timeouts on the
> server, it is difficult to find the affected KuduClient based on the
> information of rpcz. Because there may be many KuduClients on each host.
> So we want to add extra information to RpcHeader to find out the problematic
> distributed tasks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
