mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-27 22:03:31 +01:00
cda7acb35d
Tor has configure libevent to attempt up to 3 times a DNS query for a maximum of 5 seconds each. Once that 5 seconds has elapsed, it consider the query "Timed Out" but tor only gets a timeout if all 3 attempts have failed. For example, using Unbound, it has a much higher threshold of timeout. It is well defined in https://www.nlnetlabs.nl/documentation/unbound/info-timeout/ and has some complexity to it. But the gist is that if it times out, it will be much more than 5 seconds. And so the Tor DNS timeouts are more of a "UX issue" rather than a "network issue". For this reason, we are removing this metric from the overload general signal. See https://gitlab.torproject.org/tpo/network-health/team/-/issues/139 for more information. Fixes #40527 Signed-off-by: David Goulet <dgoulet@torproject.org>
6 lines
304 B
Plaintext
6 lines
304 B
Plaintext
o Major bugfixes (relay, overload):
|
|
- Don't make Tor DNS timeout trigger an overload general state. These
|
|
timeouts are different from DNS server timeout. They have to be seen as
|
|
timeout related to UX and not because of a network problem. Fixes bug
|
|
40527; bugfix on 0.4.6.1-alpha.
|