Thanks Josh. I ended up using the go-grpc-middleware for the interceptor.
Looks like Dial without the WithBlock option indefinitely tries connecting
(in the background) to the server??
During the rpc call, if the connection is not established, the retry logic
in the middleware, tries connecting
It is a persistent connection. But if you only have one backend (or, more
importantly, one hostname, such as behind a hardware load balancer and/or
proxy), the client does not create redundant connections. So there is some
downtime while it re-creates a socket connection after it gets disconnected.
Hi,
I have a question regarding the grpc Dial behavior. I have a
server, which as part of the incoming request needs to talk to another
endpoint using grpc. Currently, on the server spawn, it does grpc.Dial to
the other endpoint. and when the request comes, it does a grpc on this
establ
