The tracking issue is https://github.com/grpc/grpc/issues/7957 . The first
resolution (#1) would be to add a timer to the server to send a GOAWAY
after the connection is a certain age, allowing the proxy to choose another
backend.
I have an open question in that issue whether we also need an optio
If you are using Java, a proposed new LoadBalancer API should be able to
solve your problem:
https://github.com/grpc/grpc-java/issues/1600
It will allow LoadBalancer to create multiple connections for the same
address.
On Thursday, September 22, 2016 at 9:19:56 AM UTC-7, idan...@gmail.com
wrot
Hi,
Found this thread while searching for an answer to the same issue...
I am doing the same implementation, having a client that is directed to a
kubernetes service (DNS discovery) and I have noticed that all calls are
going to the same server.
This is a single client with multiple servers behin
