2) You can take the sleeps out of the code and try it yourself. The sleeps dont matter. If you are in a tight loop calling cq->next with multiple clients, is it inconceivable that the grpc core could starve a client? I am not familiar with your design but I think if you take a close look at it, you will be able to reason about it purely from code inspection. I witnessed it often, so it simply can’t be impossible and almost certainly isn’t implausable. If you tinker with my example I would be surprised if you can’t reproduce. I ran on ubuntu 16.04 using grpc 1.19. 3) try doing an AsyncNext with deadline = gpr_time_add(gpr_now(GPR_CLOCK_MONOTONIC), gpr_time_from_nanos(0, GPR_TIMESPAN)). I expect it to return immediately and i block.
-- 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/8984b401-19d5-491c-b6b6-0a956895bdd3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
