Any update on this? On Friday, September 17, 2021 at 12:10:22 PM UTC+5:30 Sureshbabu Seshadri wrote:
> Thanks, please find two log files one where DNS resolution failed and > another one resolved with the help of native value set to GRPC_DNS_RESOLVER > environment variable in the following share > > > https://drive.google.com/file/d/1DbipVJzdvfcLHseSGEuJvZLfJHXsXtUJ/view?usp=sharing > > Please let me know if you need any other input for analyzing the issue. > > On Thursday, September 16, 2021 at 9:43:26 PM UTC+5:30 apo...@google.com > wrote: > >> If you are able to reproduce and capture logs, then it would be great if >> you could enable the following env vars to get more debug info: >> >> GRPC_VERBOSITY=DEBUG >> GRPC_TRACE=cares_resolver,cares_address_sorting >> >> (you can add more tracers to GRPC_TRACE, but we need at least those two) >> >> Optionally, a packet trace showing DNS activity (e.g. captured by >> tcpdump) may also be helpful. >> On Thursday, September 16, 2021 at 7:04:46 AM UTC-7 sureshb...@gmail.com >> wrote: >> >>> OK, without GRPC_DNS_RESOLVER it is always reproducible, can you >>> elaborate which log type to be enabled as GRPC usually writes tons of logs >>> if we enable ALL. >>> >>> On Wednesday, September 15, 2021 at 10:41:46 PM UTC+5:30 >>> sanjay...@google.com wrote: >>> >>>> Which gRPC language are you using? Is it C++? If yes, this could be an >>>> issue with the "ares" DNS used by default. I suggest reproducing the issue >>>> with some logs and logging it at github. >>>> >>>> On Sunday, September 12, 2021 at 11:37:05 PM UTC-7 sureshb...@gmail.com >>>> wrote: >>>> >>>>> In our intranet, GRPC servers are running in different computers. >>>>> While many of the servers are connecting without any issue, there are >>>>> some >>>>> servers failed with error *"DNS resolution failed for service : >>>>> <hostname>:<port>"* >>>>> >>>>> The issue can be resolved by adding the environment variable >>>>> *GRPC_DNS_RESOLVER* with value *native.* >>>>> >>>>> *Questions: * >>>>> >>>>> 1. Since all the servers are running in the same network*, *what >>>>> could be the reason behind DNS resolution failure for some servers >>>>> only? >>>>> 2. Is adding the *GRPC_DNS_RESOLVER degrades* name resolution >>>>> performance or any other side effect. >>>>> >>>>> We need to take a decision whether this environment variable is to be >>>>> added as part of our product installation or not to avoid any similar >>>>> issues in customer environment. >>>>> >>>>> Please let know if any other input like log files required for this >>>>> issue analysis >>>>> >>>> -- 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/dcec4eb7-9d80-41ff-8e11-ce7ca163017fn%40googlegroups.com.
