The executor passed to withExecutor() is used for running callbacks on the response StreamObserver for async stubs. Since there isn't a callback for blocking stub, the executor is not used.
Regardless of blockingness of the stub, there are always network threads (e.g., Netty's EventLoopGroups) under the hood. If you want to configure that, use NettyChannelBuilder.eventLoopGroup(). On Thursday, February 28, 2019 at 4:06:29 PM UTC-8, Zareen Syed wrote: > > Hi, > > The method withExecutor() in AbstractStub class mentions that "setting > this option may not take effect for blocking calls", is there any other way > to configure the number of threads used by the client blocking stub? > > Thanks, > Zareen. > -- 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/4b507cb0-68e7-4774-8726-542a0055e021%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
