-
-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. #112191
gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. #112191
Conversation
…e implications.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, with one tiny addition of my own: you could possibly just configure a bigger thread pool. I'll wait merging for a bit in case you object to this suggestion.
Thinking about this some more, I'm curious what exactly you mean by "DNS timeouts". Is this referring to some library calling e.g. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressing @gvanrossum's comment, my suggestion would be to remove the reference to "DNS timeouts" since higher level networking libraries could treat in different ways.
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
Thanks @alex-kowalczyk for the PR, and @kumaraditya303 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
…utor usage and implications. (pythonGH-112191) (cherry picked from commit fc297b4) Co-authored-by: Alek Kowalczyk <alek.kowalczyk@gmail.com> Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
…utor usage and implications. (pythonGH-112191) (cherry picked from commit fc297b4) Co-authored-by: Alek Kowalczyk <alek.kowalczyk@gmail.com> Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
GH-120935 is a backport of this pull request to the 3.13 branch. |
GH-120936 is a backport of this pull request to the 3.12 branch. |
…cutor usage and implications. (GH-112191) (#120936) gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. (GH-112191) (cherry picked from commit fc297b4) Co-authored-by: Alek Kowalczyk <alek.kowalczyk@gmail.com> Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
…cutor usage and implications. (GH-112191) (#120935) gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. (GH-112191) (cherry picked from commit fc297b4) Co-authored-by: Alek Kowalczyk <alek.kowalczyk@gmail.com> Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
…utor usage and implications. (python#112191) Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
…utor usage and implications. (python#112191) Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
…utor usage and implications. (python#112191) Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
Proposing additional note for
asyncio.getaddrinfo
/asyncio.getnameinfo
, to document they employ the loops's default executor which might manifest in "DNS timeouts" when the executor is saturated.See also: Guido's remark at #112169 (comment)
asyncio.getaddrinfo
manifests in misleading DNS timeouts when thread pool executor is saturated #112169📚 Documentation preview 📚: https://cpython-previews--112191.org.readthedocs.build/