On Thu, May 15, 2014 at 1:41 PM, James Harrison <[email protected]> wrote: > Hi, > > So I migrated a site dealing with a quite simple Varnish config > (basically caching images and static content, passing through dynamic > requests with no modifications etc) last week. Since then I've had to > restart varnish twice due to what looks like a thread pool leak. > > Varnish is configured with a max thread count of 1000 - the other > thread options are defaults. With all defaults the problem still > occurs. This is a Debian Wheezy system using the Varnish packages (ie > not system packages). > > varnishstat shows MAIN.threads as 500 and has ~7.5k, 8k for > created/destroyed (11 for limited). Varnish has served a TB of content > since restart a day ago in this state. > > `ps auxH | grep varnish | wc -l` shows varnish has 7508 > threads/processes running. > > This graph shows the rapid increase in running threads - I restarted > varnish with the lower pool limit at the end of the 13th: > https://i.imgur.com/488IT7z.png > > Any ideas?
Hi, I remember this: https://www.varnish-cache.org/lists/pipermail/varnish-commit/2014-May/011395.html Dridi > -- > Cheers, > James > > _______________________________________________ > varnish-misc mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
