-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
io.netty.resolver.dns.DnsNameResolverTimeoutException when the application is running in Kubernetes #2978
Comments
The issue is probably well described here : https://www.weave.works/blog/racy-conntrack-and-dns-lookup-timeouts and https://blog.quentin-machu.fr/2018/06/24/5-15s-dns-lookups-on-kubernetes/ and kubernetes/kubernetes#56903 Can reactor-netty set the DNS resolution to use TCP instead of UDP ? |
@arthurzenika We do enable TCP fallback by default reactor-netty/reactor-netty-core/src/main/java/reactor/netty/transport/NameResolverProvider.java Line 553 in 9aa0877
Also you are running with an old version of Netty and there are fixes in the newer versions that might be related. |
Facing similar issue on 4.1.91.Final, seeing high address resolver time 5 - 20s and connect time in multiples of 5 seconds, some requests failing with
Facing this with EKS 1.24 and older EKS versions as well. |
@mukeshj13 Are you running with the latest Reactor Netty/Netty versions? |
This might be related to netty/netty#13660 |
Thanks for looking into this and pointing to multiple ressources. Upgrading to the reactory-netty 1.0.38 (Spring-boot-webflux 2.7.7, netty 4.1.100.Final) we get the following error :
|
@arthurzenika IMO this has to be reported to Netty project. |
Let me close this issue in favour of Netty's issue. If some additional configuration is needed in Reactor Netty we can reopen it. |
Expected Behavior
For DNS to be resolved in less than 5 minutes by reactor-netty.
Actual Behavior
This error only occurs occasionally, so it is non trivial to reproducte
Stacktrace
Steps to Reproduce
Instanciation code
Web request call code
Possible Solution
We are investing time to look into possible fixes / cache / remediation in the kubernetes infrastructure
Another fix being pursued is upgrading the various component versions, and adding a retry mecanism.
Your Environment
Versions :
The text was updated successfully, but these errors were encountered: