IDLE_TIMEOUT isn't supported in go. It's tracked in https://github.com/grpc/grpc-go/issues/1719
The PR you mentioned is a step towards this goal. But that only covers connection idleness, not at the ClientConn level (e.g. it doesn't turn down resolver and balancers) On Saturday, July 24, 2021 at 12:32:54 AM UTC-7 [email protected] wrote: > The connectivity semantics documentation [1] states that a connection > will move from READY to IDLE if no active requests have been made for > IDLE_TIMEOUT duration. > However, in Go, i don't see such a configuration, is this state used > in Go grpc implementation or is this being implemented? [2] > > Thanks, > Amit > > [1] > https://github.com/grpc/grpc/blob/master/doc/connectivity-semantics-and-api.md > [2] https://github.com/grpc/grpc-go/pull/4613 > -- 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/f515e043-09af-4e13-b9fb-8a3cf53991ebn%40googlegroups.com.
