To clarify: are you asking about doing streaming RPCs to multiple backends? If so, each RPC (which consists of multiple messages) will be sent to different backends. Once a streaming RPC is started, it will be pinned to a particular backend and not change.
On Friday, December 22, 2017 at 6:13:02 AM UTC-8, davidr...@gmail.com wrote: > > > I've been successfully used the Manual Flow Control > <https://github.com/grpc/grpc-java/tree/master/examples/src/main/java/io/grpc/examples/manualflowcontrol> > > example to make streaming async requests from one client to one server. I > have also have been successful using the kubernetes load balancer example > <https://github.com/saturnism/grpc-java-by-example/tree/master/kubernetes-lb-example/echo-client-lb-api/src/main/java/com/example/grpc/client> > > to allow one client to make round robin blocking stub requests to multiple > servers. But I'm not able to combine the two examples to allow one client > to make async requests to multiple servers. Is the Manual flow control > example by it's nature a single server technique since it uses a > ClientResponseServer relationship? > > What would be the proper way for me to throttle my streaming async > requests to multiple servers? > > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. 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/890a6d29-bcc1-4f9d-8355-bb437a1c848c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
