Hi there, Sorry for the delayed response. The reason that we don't queue RPCs is documented at https://github.com/grpc/grpc/issues/8603 : this was an issue in Ruby before we allowed C++ thread pools to be limited, but all the same reasons described in the issue apply to C++ as well. Basically, queueing can lead to deadlock (and I gave an example in that issue) so better to fail with resource exhausted instead.
- Vijay On Tuesday, October 30, 2018 at 1:30:32 AM UTC-7, [email protected] wrote: > > Am using C++ > > On Monday, 29 October 2018 23:27:25 UTC+5:30, Carl Mastrangelo wrote: >> >> What language are you using? >> >> On Sunday, October 28, 2018 at 11:30:14 PM UTC-7, [email protected] >> wrote: >>> >>> Hi, >>> >>> I want to limit number of threads in gRPC, I can limit it by setting >>> maximum number of threads. >>> But if there are requests in process for defined number of threads, next >>> RPC call immediately fails with RESOURCE_EXHAUSTED. >>> >>> Is there a way that I can queue that request and it will execute once in >>> process threads completes processing? >>> >>> >>> >>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/bd3e98cb-cda9-4526-96e5-41233533b08c%40googlegroups.com.
