How can I close all connections in a java ManagedChannel and restart them?

[yfe...@gmail.com]

Hey folks,

My understanding is that a ManagedChannel can have a number of possible connections backing it. Is there a way to kill all the connections and restart them without shutting down the ManagedChannel and creating a new one?

This has come about due to issues related to https://github.com/grpc/grpc-java/pull/5599 where I know that the application is in a bad state and would rather restart all connections than wait the 15 min for them to timeout.

Thanks!

[Jihun Cho]

can you use keepalive to make grpc aware of the bad connections? 

https://github.com/grpc/proposal/blob/master/A8-client-side-keepalive.md

[yfe...@gmail.com]

Hi Jihun!

Sadly not easily. I'm in a bit of dependency hell trying to update to > 1.21 and would then have ensure that native EPoll is used over NIO.

Hoping clearing all underlying connections might be the easy way out.

Yosef

[Eric Anderson]

It seems you are thinking of the OS-based TCP_USER_TIMEOUT. But there is also keepalive that you can configure, which is what A8-client-side-keepalive.md is talking about. It has been available for quite a while.

--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/cf774c56-845f-4fc7-af86-e329c1003324%40googlegroups.com.