Probing to see if Varnish is Alive.
Michal Taborsky - Netretail Holding
michal.taborsky at nrholding.com
Wed Sep 15 17:39:39 CEST 2010
here is how we do it. We have also a couple of varnishes sitting in
front of several backend servers. Each backend server responds to a
simple http request on URL http://220.127.116.11/ping (18.104.22.168 being the
backend server IP). We use this to check the backend server health in
our VCL (in the probe statement). We also use this URL however to check
the health of the varnish servers too. We just configured our load
balancer to access the varnish URL (http://22.214.171.124/ping, 126.96.36.199 being
the varnish IP address) and check it's http status code.
Now, the load balancer will stop sending traffic to the varnish server
either when it is down itself or when all it's backends are down, which
is essentially the same thing, because it means the varnish cannot serve
traffic. We are using restart in the VCL to make sure that single
backend failure will not trigger this. If one backend goes down, the
ping request is served by different live backend.
Does it make sense?
Dne 15.9.2010 15:25, Mohan Rao napsal(a):
> Is there a way to probe a varnish server to see if it is alive ? We
> have a couple of varnish servers that are load balanced. We would like
> the load balancer to stop sending traffic to a particular varnish
> server if we are updating that server. Is there a recommended way to
> do this ?
> Thanks & Regards,
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
chief systems architect
Netretail Holding, B.V.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the varnish-misc