-
Notifications
You must be signed in to change notification settings - Fork 213
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
Client connections resolve DNS asynchronously #3140
Conversation
async_dns_resolution_client@35292 aka 20211027.15 vs main ewma over 20 builds from 34910 to 35269 Click to see table
|
@achamayou I don't believe so. The issue described in #70 is only about the listening sockets on node start-up (which are still synchronous in this PR). This PR only changes the behaviour for client connections. |
@jumaffre indeed, thank you for pointing this out! |
DNS resolution was made synchronous in #70 for listening sockets, but isn't necessary for client connections, which could stall the host thread if the DNS resolution takes too long, causing spurious elections.
FYI, using the
socket_getaddrinfo
CLI, I've managed to hit ~4sec stall for DNS resolution in rare cases, running