varnish stopped resonding
MSchurenko at airg.com
Thu Sep 22 18:48:57 CEST 2011
How can I increase the amount of workers, just increase thread_pool_max?
It looks like there are a fair amount of sockets between varnish and the backend server that are stuck in CLOSE_WAIT. Could this be what's using all my workers?
I would like to use malloc; however our cache size is huge and, from what I read, it is better to use file if your cache will not fit all in RAM.
airG share your world
Suite 710, 1133 Melville Street
Vancouver, BC V6E 4E5
E: MSchurenko at airg.com
From: varnish-misc-bounces at varnish-cache.org [varnish-misc-bounces at varnish-cache.org] On Behalf Of Andreas Plesner Jacobsen [apj at mutt.dk]
Sent: Thursday, September 22, 2011 9:33 AM
To: varnish-misc at varnish-cache.org
Subject: Re: varnish stopped resonding
On Wed, Sep 21, 2011 at 10:15:51AM -0700, Matt Schurenko wrote:
> I'm running two varnish servers in production (ver 2.1.5). Both are using
> the same hardware and have the same amount of RAM (48GB). Last night one of
> the varnish servers stopped responding on port 80. Since we are using HAproxy
> in front of both varnish servers for load balancing this did not have much
> effect on our end users. The symptoms of the problem were either a client (
> HAproxy, telnet) could not establish a layer 4 connection to varnish or, if a
> client could establish a connection and issued an HTTP GET, varnish returned
> nothing, no HTTP headers, nothing.
Clients are stuck in the listen queue because you've run out of workers.
Are you sure that the workers are not all stuck trying to get content from the
You may be experiencing workers piling up on uncacheable urls or urls, that are
being refreshed (where the queue will wait for the first request to complete
unless you're using grace)
You may also want to consider using malloc instead of file storage.
varnish-misc mailing list
varnish-misc at varnish-cache.org
More information about the varnish-misc