Hi, You are right. It is definitely not user friendly for someone trying to set up keepalives to also have to set GRPC_ARG_HTTP2_MIN_SENT_PING_INTERVAL_WITHOUT_DATA_MS. I believe the reason for this is mostly to deal with the fact that pings in gRPC Core can originate via either of 3 methods - 1) Keepalive 2) BDP 3) grpc_channel_ping()
I can think of a few possible ways to improve experience here - 1) Reduce the default value of GRPC_ARG_HTTP2_MIN_SENT_PING_INTERVAL_WITHOUT_DATA_MS 2) Use the minimum of GRPC_ARG_HTTP2_MIN_SENT_PING_INTERVAL_WITHOUT_DATA_MS and GRPC_ARG_KEEPALIVE_TIME_MS to set the minimum ping interval without data. 3) Make GRPC_ARG_HTTP2_MIN_SENT_PING_INTERVAL_WITHOUT_DATA_MS defunct. On Wednesday, August 5, 2020 at 8:58:27 AM UTC-7 [email protected] wrote: > Hi, > can somebody explain the relation between these two time settings on a > client perspective? > > It seems to me, that GRPC_ARG_HTTP2_MIN_SENT_PING_INTERVAL_WITHOUT_DATA_MS > is the lower limit for GRPC_ARG_KEEPALIVE_TIME_MS. > But why does this GRPC_ARG_HTTP2_MIN_SENT_PING_INTERVAL_WITHOUT_DATA_MS > exists at all, when I control the rate of the ping with the KEEP_ALIVE time? > > I need to detect the interruption of long living streaming channels, that > might not transport any data for minutes or even hours. > > > > Thanks > Tobias > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/c4d04d60-65c5-4ade-9d82-69e6fdf44847n%40googlegroups.com.
