[grpc-io] Help with asynchronous streaming write
Hello, I have a C++ gRPC server implemented with Completion Queue API and I have a Python client using server-side streaming RPC. When the server writes the first event (response), it never makes it to the client but if I exit from the server side loop (waiting for updates in the event stream) after the first write, then the Python client receives the data. The write tag is completed and returned by cq->Next(). This makes me think that there is some buffering happening on the server side. I tried to fix it by using WriteOptions().write_though() but it didn't help. I didn't have to do this in the past projects. Google search doesn't seem to yield any good answers. Has anyone encountered similar problems? I am using grpc-1.52.1. Any hints or help is greatly appreciated. Thank you. -- 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 grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/5b5e43e2-8b24-4089-81c0-65d0fc22b9c9n%40googlegroups.com.
[grpc-io] Re: Help with asynchronous streaming write
After I run with: tcp,http,api I see that write succeeds ( tcp_posix.cc:1873 write: OK and chttp2_transport.cc:773 - state WRITING -> IDLE [finish writing]). Thank you. On Friday, May 5, 2023 at 7:14:48 PM UTC-4 ctmah...@gmail.com wrote: > Hello, > > I have a C++ gRPC server implemented with Completion Queue API and I have > a Python client using server-side streaming RPC. When the server writes the > first event (response), it never makes it to the client but if I exit from > the server side loop (waiting for updates in the event stream) after the > first write, then the Python client receives the data. The write tag is > completed and returned by cq->Next(). > > This makes me think that there is some buffering happening on the server > side. I tried to fix it by using WriteOptions().write_though() but it > didn't help. I didn't have to do this in the past projects. > > Google search doesn't seem to yield any good answers. Has anyone > encountered similar problems? I am using grpc-1.52.1. Any hints or help is > greatly appreciated. > > Thank you. > > > -- 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 grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/48fb3b02-883c-4c21-a316-b573134e1635n%40googlegroups.com.
[grpc-io] Re: Help with asynchronous streaming write
After I run with GRPC_BERBOSITY=debug and GRPC_TRACE=tcp,http,api I see the write is succeeding on the server, but still client doesn't receive it. tcp_posix.cc:1873] write: OK chttp2_transport.cc:773] state WRITING->IDLE [finish writing]. Thank you. On Friday, May 5, 2023 at 7:14:48 PM UTC-4 ctmah...@gmail.com wrote: > Hello, > > I have a C++ gRPC server implemented with Completion Queue API and I have > a Python client using server-side streaming RPC. When the server writes the > first event (response), it never makes it to the client but if I exit from > the server side loop (waiting for updates in the event stream) after the > first write, then the Python client receives the data. The write tag is > completed and returned by cq->Next(). > > This makes me think that there is some buffering happening on the server > side. I tried to fix it by using WriteOptions().write_though() but it > didn't help. I didn't have to do this in the past projects. > > Google search doesn't seem to yield any good answers. Has anyone > encountered similar problems? I am using grpc-1.52.1. Any hints or help is > greatly appreciated. > > Thank you. > > > -- 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 grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/1eeb605b-9a05-423a-8812-8518595ed258n%40googlegroups.com.
