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

hostname resolution #358

Closed
gquintard opened this issue Aug 20, 2021 · 2 comments
Closed

hostname resolution #358

gquintard opened this issue Aug 20, 2021 · 2 comments
Assignees

Comments

@gquintard
Copy link
Contributor

@sudazzle opened varnish/docker-hitch#5 and while there's a work around to fix it at the docker-compose level, it could be interesting to have hitch be a bit more tolerant about this and notably do an on-the-fly resolution before opening a socket.

I know varnish function the same way, but hitch doesn't have vmod_goto and vmod_dynamic to sidestep the issue.

@daghf
Copy link
Member

daghf commented Sep 1, 2021

We do already have a feature that enables Hitch to periodically refresh the backend IP number. Is this workable as a solution here?

via hitch.conf(5)

backend-refresh = <number>
--------------------------

Number of seconds between periodic backend IP lookups, 0 to disable.
Default is 0.

@gquintard
Copy link
Contributor Author

that's one of those cases where I think doing it in the critical path would make more sense, but the current solution will work. Sorry I missed it

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

No branches or pull requests

2 participants