[
https://issues.apache.org/jira/browse/KUDU-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852698#comment-16852698
]
Xu Yao commented on KUDU-2835:
------------------------------
[~adar] Thank you for your comment.
In theory, the client_id can do what I want. But currently the client_id is a
uuid, and there is no information about distributed tasks, so this will be more
difficult.
Think about it, use a client_id to find which spark task to use the KuduClient.
This may have to check the logs of many spark tasks.
Maybe we can extend the client_id information under the condition that the
client_id is unique. But I think it might be better to add an optional field to
the RequestIdPB.
> 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
> 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)
