flushing cache doesn't seem to make varnish know about less

Tollef Fog Heen tfheen at linpro.no
Mon Jan 12 11:34:40 CET 2009


]] Timothy Ball 

| a programming error caused varnish to think there were billions of
| pages it had to know about. bug is quashed but varnish doesn't seem to
| know
| 
| # this is a line from top
|  3596  0.2 28.3g  28g 3808  256  57m 1916   12    0 S  20   0    0 varnishd
| # this is a line from ps auxwww
| nobody    3596  0.1  0.1 29681936 3968 ?       Sl   04:24   0:00
| /opt/varnish/sbin/varnishd -a 10.13.37.1:80 -h classic -f
| /etc/varnish/default.vcl -T 127.0.0.1:6082 -t 120 -w 1,500,20
| 
| i tried doing url.purge ".*" and url.purge "." to no avail.

url.purge does not actively go out and remove the objects; they'll be
picked up by the LRU cleaner after a while.

If you need to recover the memory, you can do a quick «stop» and then
«start» in the CLI, but this will naturally nuke your complete cache, so
it can't be used if you just wanted to remove some bits.

-- 
Tollef Fog Heen 
Redpill Linpro -- Changing the game!
t: +47 21 54 41 73



More information about the varnish-misc mailing list