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 "Joe McDonnell (Jira)" <ji...@apache.org> on 2026/03/20 15:37:00 UTC

[jira] [Created] (IMPALA-14845) RpcRecvrTime should keep initial receiver startup delay separate

Joe McDonnell created IMPALA-14845:
--------------------------------------

             Summary: RpcRecvrTime should keep initial receiver startup delay separate
                 Key: IMPALA-14845
                 URL: https://issues.apache.org/jira/browse/IMPALA-14845
             Project: IMPALA
          Issue Type: Task
          Components: Distributed Exec
    Affects Versions: Impala 5.0.0
            Reporter: Joe McDonnell


RpcReceiverTime/RpcNetworkTime are used to understand the performance of RPCs for KRPC data stream senders. One complication for RpcReceiverTime is that a slow startup of the receiver can result in a high value once without impacting subsequent values. For example, if we set --stress_datastream_recvr_delay_ms=5000 to force the receiver to be delayed by 5 seconds, the max value for RpcReceiverTime would be 5 seconds. It would be useful to make a distinction between the setup delay vs the maximum seen after that point.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org