Varnish only resolve the ip on startup

[Guillaume Quintard]

I think it makes sense for Varnish to natively support backends changing
their IPs. I do get the performance argument but now that there is a
cloud/container market and that Varnish has proven to be useful in it, this
basic functionality should be brought in.

Would it be acceptable to add a "host_string" to vrt_endpoint and fill it
if the VCL backend isn't an IP, then, we can add another cp_methods to
cache_conn_pool.c to use it? This way IPs are still super fast, and
hostnames become actually useful and a bit less confusing?

-- 
Guillaume Quintard


On Sun, Oct 3, 2021 at 9:07 AM Léo <leo.lelievre at protonmail.com> wrote:

> Hello,
> While setting up a docker-compose with a cache powered by varnish I came
> across an issue when recreating a container that varnish depends on. After
> the recreation varnish doesn't try to retrieve the new local ip. I've been
> told this is an upstream varnish issue (
> https://github.com/varnish/docker-varnish/issues/41). I have found some
> ways to solve the problem, but will an appropriate solution be considered ?
>
> Thanks in advance,
> Have a good day,
> Léo Lelievre
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20211004/f3839fff/attachment.html>