[
https://issues.apache.org/jira/browse/KUDU-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852641#comment-16852641
]
Adar Dembo commented on KUDU-2835:
----------------------------------
Would the existing client_id field work for you? It's globally unique,
generated per-KuduClient instance:
{noformat}
// The Id of a retriable RPC, whose results should be tracked on the server
(see result_tracker.h).
// This also includes some information that is useful for execution/garbage
collection.
message RequestIdPB {
// The (globally unique) id of the client performing this RPC.
required string client_id = 1;
// The (per-client unique) sequence number of this RPC.
required int64 seq_no = 2;
// The sequence number of the first RPC that has not been marked as completed
by the client.
// Unset if there isn't an incomplete RPC.
required int64 first_incomplete_seq_no = 3;
// The number of times this RPC has been tried.
// Set to 1 in the first attempt.
required int64 attempt_no = 4;
}
{noformat}
Looks like it might not be set for every RPC, only for retriable ones. But
presumably it could be used universally.
> 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)
