file storage engine overflow and 503 error

[Sean Allen]

For the edification of future parties, check out the nuke limit option. We
were pulling back some objects that were larger than 50x average object
size so nuking didn't create enough space.


On Wed, May 8, 2013 at 5:22 AM, Sean Allen <sean at monkeysnatchbanana.com>wrote:

> Varnish 3 series.
>
> We recently switched one of our varnish caches from being having a malloc
> based storage to file based. When the cache overflowed using the malloc
> based one, an older item was nuked and the requested item was returned.
>
> When we overflowed the file storage engine cache yesterday, varnishstat
> showed the items being evicted but would return a 503 for the requested
> item and in varnishlog, was showing it couldn't allocate storage during the
> deliver phase for the requested item.
>
> What do I need to do to change to not have a cache overflow result in 503
> errors?
>
>
> --
>
> Ce n'est pas une signature
>



-- 

Ce n'est pas une signature
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20130510/dfef750f/attachment.html>