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 behind the "service" identity.
Is there any way to bypass is so that each call will actually choose a
random server in the service pool?
On Thursday, October 8, 2015 at 12:41:27 AM UTC+3, Johan Jian An Sim wrote:
> Thanks, guys. I will do some study on that.
>> Each RPC is a different HTTP request, but generally on the same TCP
>> connection (via HTTP/2 multiplexing). So if you are using an HTTP load
>> balancer then requests would use your various servers. If you are using a
>> TCP load balancer then all requests from a client would go to the same
>> server, until that connection was broken.
>> Note that streaming RPC are each a single HTTP request; all request
>> messages in the stream go to the same server.
>> On Tue, Oct 6, 2015 at 9:54 PM, Johan Jian An Sim <joha...@gmail.com
>>> I am looking at the gRPC Go which logs the events/requests to net/trace.
>>> When I look at that, I get a hint that client are tied to a server. Want to
>>> see if I am wrong about this.
>>> So if I have 3 servers ready (behind Kubernetes service/load balancer)
>>> and only 1 client is going to connect. Is the client's request always going
>>> to 1 server (the server that it establish connection initially)?
>>> 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
>>> To post to this group, send email to grp...@googlegroups.com
>>> To view this discussion on the web visit
>>> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.