Hello, I am interested in the following behavior: Is it possible to create a per-connection load balancing? In other words create a stub on the client side, so that dns resolution will be performed only on stub creation and all rpc calls on that stub will be invoked on the same grpc server? I see that there are two load balancing policies available: round_robin and pick_first.
If I use "round_robin" I see that it implements a per-call balancing and different rpc calls on the same stub are resolved to different grpc server. If I use "pick_first"(the default as far as I see), all the rpc calls on the same stub will go to the same server, which is good, but from what I understand every subsequently created channel will also be resolved to the same server as soon as it is responsive. Any thoughts on how I can achieve that? Thank you in advance. -- 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/5343e052-e66f-48b8-8cc9-e316170aeecf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
