This is not the right forum for debugging application code. Please try StackOverflow for that, since the number of grpc users is a lot more than the number of grpc developers and one of them may decide to spend some time on this for you. This forum is best for clarifications or discussions of feature requests.
As a small point, you have a sleep and many couts in your async code processing code, which is not a good idea since it prevents other operations during that time. It likely won't solve your issue, but you're preventing the CQ::Next loop from running so no more tags can be posted in this time. You should keep that section as fast as possible. As far as serving clients in order, gRPC does not enforce any ordering for clients (we have load balancing options for picking _servers_), so that is probably due to your code or whenever threads get to run. On Tuesday, March 12, 2019 at 2:31:24 PM UTC-7, Jeff wrote: > > I see now that the issue was that client 1 wasn’t terminating, and so the > server never moved on to client2. I expected the server would alternate > (potentially non-deterministically) between clients, and not serve them in > order. Is there a way around this? -- 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/b4498658-07bb-4284-9e48-b99d6b2e4e18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
