OOM caused by infinite loop in response

Delacroix, Gauthier Gauthier.Delacroix at coreye.fr
Thu Sep 20 13:52:51 CEST 2012

It’s coming from the backend.

Varnish cannot cache the response since it never ends.

De : Nick Tailor [mailto:nick.tailor at gmail.com]
Envoyé : jeudi 20 septembre 2012 12:35
À : Delacroix, Gauthier
Objet : Re: OOM caused by infinite loop in response

If it's coming from the cache set the ttl higher for objects cached so it serves cached content that you know is working until u fix the issue

Sent from my iPhone

On Sep 20, 2012, at 2:40 AM, "Delacroix, Gauthier" <Gauthier.Delacroix at coreye.fr<mailto:Gauthier.Delacroix at coreye.fr>> wrote:

I have a varnish instance going out of memory because of an infinite loop in a chunked backend response.

The app is sending the same string over and over, resulting in more than 4GB to varnish in 10 minutes…until it crashes.

The dev team is fixing the bug in the backend app but I’d like to avoid varnish crashes for this kind of problem.

I have seen the “http_resp_size" option in the doc but it seems to only handle headers size and I haven’t seen anything about response body limit.

Is there a way to drop connection when response body exceeds a maximum size ?

Thanks !

varnish-misc mailing list
varnish-misc at varnish-cache.org<mailto:varnish-misc at varnish-cache.org>

Ce message a ete verifie par MailScanner.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20120920/4d08f148/attachment.html>

More information about the varnish-misc mailing list