Varnish 2.0.4 health check and startup question

[Ken Brownfield]

You should check the archives and the Varnish site.  A feature to enable
"priming" the health checks was introduced in r4185 and released with 2.0.5
I believe.  I would suggest you use the latest 2.1 release and set the
.initial probe variable equal to your threshold.
-- 
Ken



On Tue, Oct 19, 2010 at 4:30 AM, Cosimo Streppone <cosimo at streppone.it>wrote:

> I'm using Varnish 2.0.4 (but IIUC, 2.1 and trunk
> seem to behave the same way) with backend health checks:
>
>  backend b1 {
>     .host = "localhost";
>     .port = "8080";
>
>     # Disabled to avoid the 15s startup time
>     #.probe = {
>     #   .url = "/ping.html";
>     #    .interval = 5s;
>     #    .timeout = 1s;
>     #    .window = 5;
>     #    .threshold = 3;
>     #}
>  }
>
> Every time I restart varnish I can see
> through debug.health that it's waiting for the
> b1 backend to become healthy.
>
> In my case that takes 15s (.interval * .threshold),
> so restarting varnish with perfectly fine backend(s)
> causes 15s of black out.
>
> Is there a reason for the initial backend state
> to be "sick" instead of "healthy"?
>
> Thanks,
>
> --
> Cosimo
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20101019/d9ea75ae/attachment-0003.html>