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

Add option to not close server connections when DNS resolution changes #882

Open
lukmajercak opened this issue Jul 6, 2023 · 0 comments · May be fixed by #881 or #905
Open

Add option to not close server connections when DNS resolution changes #882

lukmajercak opened this issue Jul 6, 2023 · 0 comments · May be fixed by #881 or #905

Comments

@lukmajercak
Copy link

lukmajercak commented Jul 6, 2023

What

Currently, when a host is resolved, pgbouncer checks all server connections for this host and tags connections using IPs not found in the new resolved list as dirty (close_needed). It would be helpful to be able to disable this behavior. This would help avoiding connection churn in scenarios where, for example, the host might return a list of different IP addresses every time (think weighted routing in Route53).

Another option to help with these scenarios would be to provide an admin command like RELOAD_DNS which would force host resolution regardless of the host's DNS TTL (dns_max_ttl).

How

Options:

@lukmajercak lukmajercak linked a pull request Jul 6, 2023 that will close this issue
@lukmajercak lukmajercak linked a pull request Jul 25, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant