[
https://issues.apache.org/jira/browse/KUDU-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034481#comment-17034481
]
ASF subversion and git services commented on KUDU-2996:
-------------------------------------------------------
Commit de3b76466ff8dc8cd85ce2f218f54e71067d013b in kudu's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=de3b764 ]
KUDU-2996: trace when rpc_duration_too_long_ms exceeded
Change-Id: I20d9b5e318f4a987051f1f7c2cd5b1d92c61bd05
Reviewed-on: http://gerrit.cloudera.org:8080/15197
Tested-by: Alexey Serbin <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
> Log trace when --rpc_duration_too_long_ms is exceeded
> -----------------------------------------------------
>
> Key: KUDU-2996
> URL: https://issues.apache.org/jira/browse/KUDU-2996
> Project: Kudu
> Issue Type: Improvement
> Components: rpc
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Fix For: 1.12.0
>
>
> According to a conversation with [~adar], the usual way to get a trace for a
> slow RPC in Kudu is to set a deadline.
> In Impala we don't use RPC deadlines, so would like to get RPC traces when
> --rpc_duration_too_long_ms is exceeded. In this case there is already
> logging, but only metrics are included:
> https://github.com/cloudera/kudu/blob/978cf39/src/kudu/rpc/rpcz_store.cc#L268
> We should log the trace in this case. Adar pointed out that we should not log
> a redundant trace if it was already logged for the RPC deadline.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
