You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi again, I have client-rpc-server-streaming that looks very similar to yours here and which is used in an app that has both grpc clients and servers. To shut them down cleanly I am avoiding calling GrpcContext::stop() and instead we only call m_server->Shutdown(). AFAICS though, this is not causing the grpc clients methods to return false and exit. In my case this is hanging forever here
I am wondering what is the proper way of shuting down the clients as well. Should I set a deadline on all my calls so they exit and I can check a flag to decide whether to retry or exit? But that wouldn't work well with streaming since in this case I want the requests to not timeout, otherwise I would be reconnecting too often to the peer.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi again, I have client-rpc-server-streaming that looks very similar to yours here and which is used in an app that has both grpc clients and servers. To shut them down cleanly I am avoiding calling
GrpcContext::stop()
and instead we only callm_server->Shutdown()
. AFAICS though, this is not causing the grpc clients methods to returnfalse
and exit. In my case this is hanging forever hereI am wondering what is the proper way of shuting down the clients as well. Should I set a deadline on all my calls so they exit and I can check a flag to decide whether to retry or exit? But that wouldn't work well with streaming since in this case I want the requests to not timeout, otherwise I would be reconnecting too often to the peer.
Thanks.
The text was updated successfully, but these errors were encountered: