[grpc-io] Re: High CPU cost due to a SpinLock in CompletionRegistry.Register

I got a chance to continue investigating this issue. I ran the tests several more times, and broke with a debugger when I saw that the process gets stuck (also, the CPU spikes at the same time). In all the cases I checked I saw the same pattern: One thread that is holding the SpinLock and has a

Re: [grpc-io] Re: c++: gRPC shutdown() hangs for ever

I have also experienced the same issue in my work environment. Our work around was to have N second timeout and check a shutdown flag and then call shutdown. > > On Feb 9, 2022 at 3:54 PM, (mailto:grpc-io@googlegroups.com)> wrote: > > > Would you capture the

[grpc-io] Re: client StreamObserver is always getting messages in sequence

adding the sleep for every 5th thread is to introduce a delay in every 5th message to make it loose the order but that did not happen. interestingly i am getting messages one by one. at server side i could see all messages are printed immediately so its not like client is requesting one by one.

[grpc-io] Re: c++: gRPC shutdown() hangs for ever

Would you capture the call-stack when Shutdown function appears to hang? On Wednesday, February 2, 2022 at 10:24:14 PM UTC-8 Anh Tran wrote: > The last commit on my local copy of gRPC is 06 Jan 2022, so not that old. > On Thursday, February 3, 2022 at 4:51:16 AM UTC+10 Easwar Swaminathan >

Re: [grpc-io] Re: GRPC Client Server Communication

The gRPC-on-gRPC tunnel including the reverse-tunnel use-case is described in this PR https://github.com/grpc/grpc-java/pull/3987 . You may want to look into it. On Wed, Feb 9, 2022 at 10:37 AM 'Yuri Golobokov' via grpc.io < grpc-io@googlegroups.com> wrote: > Normally gRPC client creates its own

[grpc-io] Re: GRPC Client Server Communication

Normally gRPC client creates its own TCP connection(s) to communicate with a gRPC server. I am not aware of an option to reuse some existing TCP connection. Can you provide more details on problems you are trying to solve? What is the reasoning behind this architecture? Why do you want gRPC

[grpc-io] Re: client StreamObserver is always getting messages in sequence

When executor gets callExecutor.execute(new MessagesAvailable()); inside MessageAvailable there is a loop: while ((message = producer.next()) != null) {