I am not sure I completely understand the question but I'll give it a shot. On any new RPC (can either be unary or streaming), after load-balancing is done, gRPC ends up choosing a backend server for that RPC. If there isn't an existing transport connection to that backend, a connection is started and a stream is started on that connection. For the entire duration of the RPC, the stream remains on the same transport and hence the same backend.
On Sunday, November 7, 2021 at 9:35:26 PM UTC-8 noahc...@gmail.com wrote: > I have a set up where I have 1 gRPC-client serving multiple backend > gRPC-servers. Now I want that the packets(flows) in each RPC call are > mapped to 1 particular instance of gRPC-server. The mapping could be based > on a 5 tuple hash(Source IP, port, Dest IP, port, Protocol) > Is there some way to achieve this? As I am of the idea that gRPC uses a > single long-lived session? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/96eb919b-b23e-462a-bcdb-a57deafc0ecdn%40googlegroups.com.
