minio

Commit Graph

Author	SHA1	Message	Date
Harshavardhana	c222bde14b	fix: use common logging implementation for DNSCache (#11284 )	2021-01-15 14:04:56 -08:00
Anis Elleuch	0e0c53bba4	tests: Lower expectation in addr selection in rand cache dialer (#10739 ) Test TestDialContextWithDNSCacheRand was failing sometimes because it depends on a random selection of addresses when testing random DNS resolution from cache. Lower addr selection exception to 10%	2020-10-22 09:35:32 -07:00
Harshavardhana	bd2131ba34	add DNS cache support to avoid DNS flooding (#10693 ) Go stdlib resolver doesn't support caching DNS resolutions, since we compile with CGO disabled we are more probe to DNS flooding for all network calls to resolve for DNS from the DNS server. Under various containerized environments such as VMWare this becomes a problem because there are no DNS caches available and we may end up overloading the kube-dns resolver under concurrent I/O. To circumvent this issue implement a DNSCache resolver which resolves DNS and caches them for around 10secs with every 3sec invalidation attempted.	2020-10-16 14:49:05 -07:00

Author

SHA1

Message

Date

Harshavardhana

c222bde14b

fix: use common logging implementation for DNSCache (#11284 )

2021-01-15 14:04:56 -08:00

Anis Elleuch

0e0c53bba4

tests: Lower expectation in addr selection in rand cache dialer (#10739 )

Test TestDialContextWithDNSCacheRand was failing sometimes because it depends
on a random selection of addresses when testing random DNS resolution from cache.

Lower addr selection exception to 10%

2020-10-22 09:35:32 -07:00

Harshavardhana

bd2131ba34

add DNS cache support to avoid DNS flooding (#10693 )

Go stdlib resolver doesn't support caching DNS
resolutions, since we compile with CGO disabled
we are more probe to DNS flooding for all network
calls to resolve for DNS from the DNS server.

Under various containerized environments such as
VMWare this becomes a problem because there are
no DNS caches available and we may end up overloading
the kube-dns resolver under concurrent I/O.

To circumvent this issue implement a DNSCache resolver
which resolves DNS and caches them for around 10secs
with every 3sec invalidation attempted.

2020-10-16 14:49:05 -07:00

3 Commits