Skip to content
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

remove host-cache-size=0/skip-name-resolve #509

Open
wants to merge 1 commit into
base: next
Choose a base branch
from

Conversation

grooverdan
Copy link
Member

Container environment can depend on a HOSTNAME of
the source container being resolvable. The resolution is cached so shouldn't be an impact.

@mmontes11 thoughts?

Container environment can depend on a HOSTNAME of
the source container being resolvable. The resolution is
cached so shouldn't be an impact.
@mmontes11
Copy link
Contributor

mmontes11 commented May 16, 2023

thanks for bringing this up. It shouldn't be an issue for the Kubernetes DNS resolution perspective

@grooverdan
Copy link
Member Author

grooverdan commented May 17, 2023

Is it actually useful? MARIADB_ROOT_HOST of a hostname like 'monitor' would enable the monitor container access to the server as root, regardless of IP of the 'monitor' container (with this merged).

Speed of DNS resolution, is cited as the reason for this setting, however I think container environment will only have a limited number of hosts connecting, well within the default host_cache_size. These values are cached. Resolution is through getnameinfo, consulting the /etc/hosts before DNS (per /etc/nsswitch.conf). From what I've seen container runtimes implement the reverse DNS ok, so this should be ok.

Part of the goal here is just returning the container to the default configuration of the server as much as possible.

@grooverdan
Copy link
Member Author

Server task to reduce possible impacts of this, particularly on users with IP or wildcard to not required DNS lookups - https://jira.mariadb.org/browse/MDEV-31323. So I'm going to treat this as a pre-req.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants