1. This would depend on the settings that you've configured for keepalive. Note that this doc is specific to gRPC Core and dependents. 2. Again, for Core and dependents, at present the idle timeout is disabled by default. GRPC_ARG_CLIENT_IDLE_TIMEOUT_MS is the channel arg to specify the modify this behavior. On Monday, January 17, 2022 at 10:46:54 PM UTC-8 Roshan Chaudhari wrote:
> I am trying to understand how keepalive or idle connection works with > gRPC. I have bidirectional streaming RPC, where I create session and do > nothing so that there is no activity on the channel. > > 1. If there is no activity, GRPC_ARG_KEEPALIVE_TIME_MS signal will be > blocked (https://github.com/grpc/grpc/blob/master/doc/keepalive.md#faq) > and connection will be closed after this interval, however, it does not > terminate and I see keepalive ping is sent and received. why? > > 2. If we do not set any params, is there any timeout after which > connection will be automatically closed? If yes, how do I change this > behaviour, which param? -- 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 grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/2f487145-429a-4c10-a64e-0aabb9264a18n%40googlegroups.com.
