Re: [grpc-io] flow control problem in GRPC C++ release v1.25.0

2020-12-16 Thread 'yas...@google.com' via grpc.io
That's some really good investigation! Kudos! The transport layer (chttp2) does not really care whether the application is using the async API or the sync API. What matters really is whether there is a thread that is polling the underlying fds. For the sync API, this generally happens through

Re: [grpc-io] flow control problem in GRPC C++ release v1.25.0

2020-12-14 Thread 韩飞
update : after I use sync mode on the client side, this problem is fixed. Does it mean a bug of a mixed use of sync and async mode? On Tue, Dec 15, 2020 at 3:11 AM 韩飞 wrote: > I use GRPC C++ lib in my distributed SQL engine. I use server stream that > client side sends "connect" request then

[grpc-io] flow control problem in GRPC C++ release v1.25.0

2020-12-14 Thread 韩飞
I use GRPC C++ lib in my distributed SQL engine. I use server stream that client side sends "connect" request then the server side sends data packets by a *sync writer* and client side receive data packets by a *async reader*. I use a single stream to pass massive data and be sure that the