Hi, Don't want to make this a bigger deal than it really is, but can we conclude from this thread then that health checks are mandatory to avoid this problem ? Or is there something that can be done internally with regards to retrying a failed DNS lookup ?
Thanks, Jorg On Friday, September 29, 2017 at 9:15:56 AM UTC+2, Jorg Heymans wrote: > > > On Friday, September 29, 2017 at 1:08:22 AM UTC+2, Kun Zhang wrote: >> >> >> >> On Wednesday, September 27, 2017 at 4:20:03 AM UTC-7, Jorg Heymans wrote: >>> >>> Happy to see this being posted. We are running into this as well, it >>> happens once every couple of weeks we have no idea why. Indeed server side >>> we don't see anything in the logs it's as if nothing is going on. When it >>> happens we restart the services though, not the client application and it >>> makes the problem go away. The client does not seem to be able to recover >>> from it. It seems to be an issue only in production, presumably because the >>> client applications and services do not get restarted as much as in test ? >>> >> >> Can you clarify this part? Did or did not the client recover from it >> after you restarted the services (servers?) ? If not, what does "it makes >> the problem go away" mean? >> > > Sorry for the confusion. The client is able to successfully make grpc > calls again once the server is restarted. Without a server restart, the > client stays in this error state indefinitely. Hope this is more clear. > > Jorg > -- 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/1ae129f1-36dd-405c-bcb0-2ac28b6992ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
