That's mysterious, do you know what the state of the DNS records are when this occurs? And would it be possible for you to upgrade your gRPC library and try to reproduce this? v1.36.4 is over a year old, and a fair handful of bug fixes have gone in since then.
We've been unable to reproduce this failure in testing, and would > appreciate any pointers: > Regarding that, are you able to reproduce the conditions in which the failure occurs, or are they maybe not fully understood? e.g., run a local DNS server for testing, and modify its records. > > - what is supposed to re-kick a new DNS resolve if the server list is > empty? > - where to check in the resolver code for an empty server list? > - or any other ideas for how to track down the problem > > > We're using grpc v1.36.4 w/ libcares2 1.14 > > Regards, > Peter Hurley > -- 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/306779dd-0a68-4b95-851e-0a5979a4e872n%40googlegroups.com.
