[
https://issues.apache.org/jira/browse/KUDU-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770178#comment-17770178
]
ASF subversion and git services commented on KUDU-3514:
-------------------------------------------------------
Commit 0d837c5aac482fbe46170e26ac45e5ad951eecec in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=0d837c5aa ]
[rpc] KUDU-3514 add metric to track per-RPC timeouts
This patch introduces a new per-RPC counter to accumulate stats on the
responses that have been sent to the client side past the deadline.
It should help troubleshooting of particular scenarios and provide
a glimpse of what part of requests to a particular RPC method timed out
while being processed.
This patch also includes test scenarios to cover the functionality
of the newly introduced metric.
Change-Id: I0a3cef63475c26f7936d5be7a0072a72332b7c88
Reviewed-on: http://gerrit.cloudera.org:8080/20517
Tested-by: Kudu Jenkins
Reviewed-by: Zoltan Martonka <zmarto...@cloudera.com>
Reviewed-by: Abhishek Chennaka <achenn...@cloudera.com>
> Introduce per-RPC metric of responses sent past the client-defined deadline
> ---------------------------------------------------------------------------
>
> Key: KUDU-3514
> URL: https://issues.apache.org/jira/browse/KUDU-3514
> Project: Kudu
> Issue Type: Improvement
> Components: master, server, tserver
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
> Labels: metrics, supportability
>
> As of Kudu 1.17.0, there is per-RPC histogram for processing times of remote
> calls: {{handler_latency_xxx}}, where the {{xxx}} suffix stands for the RPC
> interface and method name. There is also service-wide
> {{rpc_incoming_queue_time}} historgram.
> However, even using these two metrics above it's hard to definitely tell how
> many calls of a particular RPC method timed out while being processed by a
> Kudu server, even if the client-defined timeout is known, fixed, and the same
> for all the RPCs processed by a Kudu server.
> It would be nice to introduce a new per-RPC counter to accumulate stats on
> the responses that have been sent back to the client side already past the
> deadline. That would help troubleshooting of particular scenarios and
> provide a glimpse of what part of requests to a particular RPC method timed
> out while being processed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
