From: Alberto Salvia Novella <es20490446e@gmail.com>
To: glibc developers <libc-alpha@sourceware.org>
Subject: Fwd: Increasing resolver timeout
Date: Fri, 8 Nov 2019 18:20:48 +0100 [thread overview]
Message-ID: <7c4eba31-5da1-0d9a-7115-1dc00e0c0c04@gmail.com> (raw)
In-Reply-To: <d61fa44c-05a9-aa88-aeb6-07735d582330@gmail.com>
For example we have the following bug:
$ time ping -c1 "google.com""
0% packet loss
0m5,064s
$ time (ip=$(getent ahostsv4 "google.es" | awk '{ print $1 }' |
head -n1); ping -c1 "${ip}")
0% packet loss
0m0,042s
The extra time on the first case it's caused by a router mistakenly not
returning the IPv6 DNS reply, so the command just sits till it timeouts.
The point is this, the bug has been there for a long time unnoticed
simply because with 5s timeout the delay simply felt within normal. It
wasn't till I started programing server stuff where I noticed that
retrieving the data just took so long.
So probably we would be better having a longer timeout, like about 10s.
So if there is any network anomaly it would be obvious to any person
operating it.
Alberto <https://es20490446e.wordpress.com>
parent reply other threads:[~2019-11-08 17:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <d61fa44c-05a9-aa88-aeb6-07735d582330@gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c4eba31-5da1-0d9a-7115-1dc00e0c0c04@gmail.com \
--to=es20490446e@gmail.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).