[
https://issues.apache.org/jira/browse/KUDU-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370494#comment-16370494
]
Todd Lipcon commented on KUDU-2313:
-----------------------------------
It seems like if we track the incoming payload size we should probably track
the response size too. But now we're talking about adding a lot of extra
histograms (probably 60+ given the number of RPCs)
What granularity are you looking for? If we use a pretty coarse histogram (eg 1
significant figure) the memory requirements won't be that big. Would that be
enough?
Also I wonder if it would be enough to just record this as part of the sampled
RPCs shown in /rpcz rather than a full histogram. Can you share more about the
anticipated use case?
> Record incoming RPC payload size in histogram
> ---------------------------------------------
>
> Key: KUDU-2313
> URL: https://issues.apache.org/jira/browse/KUDU-2313
> Project: Kudu
> Issue Type: Bug
> Components: rpc
> Affects Versions: 1.6.0
> Reporter: Lars Volker
> Priority: Major
>
> Currently we track the handling latency of incoming RPC calls in
> \{{RpcMethodInfo::handler_latency_histogram}}. For Impala, it would also be
> helpful to track the payload size in a similar way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
