Thanks for your reply.
I have considered those options and it would not work for me.
1. The streaming rpc will provide incremental on change data from server to
the client, if I set the deadline the streaming rpc gets reestablished if
server is still connected and have no data to send within
You can set a deadline to your stream. Re-issuing the rpc is not really a
problem because a failed read at the client means the rpc is done at the
server or failed somehow anyway.
Or you can configure client side channel keep alive by adding channel
arguments: GRPC_ARG_KEEPALIVE_TIME_MS and
Hi,
Can you help me understand how did you overcome this issue. I too have a
client that invokes streaming rpc and it gets blocked in ClientReader::Read.
I cant set a timeout as it would mean the rpc needs to be invoked again
after the timeout.
I need a way to reestablish the server connection
