You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Xu Yao (JIRA)" <ji...@apache.org> on 2019/05/31 03:48:00 UTC

[jira] [Updated] (KUDU-2835) Add costom id in RpcHeader

     [ https://issues.apache.org/jira/browse/KUDU-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xu Yao updated KUDU-2835:
-------------------------
    Summary: Add costom id in RpcHeader  (was: Add costom id in RPCHeader)

> Add costom 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)