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 08:38:00 UTC

[jira] [Comment Edited] (KUDU-2835) Add custom id in RpcHeader

    [ https://issues.apache.org/jira/browse/KUDU-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852801#comment-16852801 ] 

Xu Yao edited comment on KUDU-2835 at 5/31/19 8:37 AM:
-------------------------------------------------------

This is a good question. I think there are three main reasons:
1. Most of our distributed jobs are run by resources of online services. These resources are constantly changing, so it is difficult to deploy monitor-agents.
2. We have a lot of distributed jobs running (there are tens of thousands of jobs running at the same time), and using kudu is part of it. It is difficult to track only the distributed jobs of kudu.
3. We are more concerned about the timeout caused by service-side than the networking issue. Because the work environment of distributed jobs may be poor.





was (Author: oclarms):
This is a good question. I think there are three main reasons:
1. Most of our distributed jobs are run by resources of online services. These resources are constantly changing, so it is difficult to deploy monitor-agents.
2. We have a lot of distributed jobs running (there are tens of thousands of jobs running at the same time), and using kudu is part of it. It is difficult to track only the distributed jobs of kudu.
3. We are more concerned about the timeout caused by service-side than the networking issue.



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