It might be worth setting the deadline on the RPC. Also, try setting the keepalive timer using the channel args GRPC_ARG_KEEPALIVE_TIME_MS and GRPC_ARG_KEEPALIVE_TIMEOUT_MS
On Wednesday, May 9, 2018 at 3:38:48 PM UTC-7, chnex wrote: > > I have a grpc c++ client code to connect to a server (external to my > code). When the server crashes, my code will detect, restart the server > process, and re-create a client object to connect. It works for the first > crash. but for the second crash, the client object seems stuck in the first > call (I looked at grpc log: the call is invoked, but the message never > reaches the server), as well as the later calls. This applies to both async > (completion queue receives nothing) and sync calls (stuck). any > pointers/helps? Thanks a lot! The server process always use a same unix > socket for communication. I delete it every time after detecting the crash > and before restarting the server process. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/e66ab04a-c883-4caa-b8e6-e8406b6e07ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
