Thanks for the information. Apologies for my previous message, which was follow-up on a completely different question. (I thought I'd asked it in this group, but apparently not.)
On Wednesday, November 1, 2017 at 11:36:34 AM UTC-5, Eric Anderson wrote: > > grpc.max_connection_age_ms is a server-side option. For documentation, see > gRFC > A9 Server-side Connection Management > <https://github.com/grpc/proposal/blob/master/A9-server-side-conn-mgt.md>. > This should work on server-side without issue. If you're concerned about > resources, use grpc.max_connection_idle_ms > instead. grpc.max_connection_age_ms is mainly useful when using a TCP-based > (L4) load balancer. > > The client-side option you're looking for... isn't implemented. I've filed > https://github.com/grpc/grpc/issues/13212 . That said, depending on the > details of what you're doing, it may be better to use the existing > server-side options. (It all depends on whom you're trying to help: use > client-side option for client optimization, server-side option for server > optimization.) > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/68aba158-0eed-4931-a00d-47ebfb09d823%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
