You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Sahil Takiar (Jira)" <ji...@apache.org> on 2020/09/03 17:02:00 UTC
[jira] [Commented] (IMPALA-10142) Add RPC sender tracing
[ https://issues.apache.org/jira/browse/IMPALA-10142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190302#comment-17190302 ]
Sahil Takiar commented on IMPALA-10142:
---------------------------------------
Actually this only really be useful if the RPC response includes some trace information as well. Currently, the {{TransmitDataResponsePB}} just includes the {{receiver_latency_ns}}. Adding that into the trace would be useful, other things such the timestamp when the RPC was received by the receiver, time in queue, etc. would be useful as well.
> Add RPC sender tracing
> ----------------------
>
> Key: IMPALA-10142
> URL: https://issues.apache.org/jira/browse/IMPALA-10142
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Sahil Takiar
> Priority: Major
>
> We currently have RPC tracing on the receiver side, but not on the the sender side. For slow RPCs, the logs print out the total amount of time spent sending the RPC + the network time. Adding tracing will basically make this more granular. It will help determine where exactly in the stack the time was spent when sending RPCs.
> Combined with the trace logs in the receiver, it should be much easier to determine the timeline of a given slow RPC.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org