Date: Sun, 07 Jan 2018 17:51:34 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 223065] INDEX file truncated from time to time Message-ID: <bug-223065-13-DrlBPo4Qwx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223065-13@https.bugs.freebsd.org/bugzilla/> References: <bug-223065-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223065 --- Comment #10 from Wolfram Schneider <wosch@FreeBSD.org> --- As far as I understand varnish: the front-end has a fast connection to the backend. The backend delivers the data fast (>1GBit/s) Varnish needs to allocate memory to cache the data from the backend. If the malloc() call fails, varnish may return truncated resul= ts. If we know the exact file size in advance, then your client will report an error message due the mismatch between the content-length and the received bytes. For dynamic content, you will get rotten results - that's horrible. I do not understand why varnish fails to cache a 2MB "big" file. The machine has several GB RAM reserved for varnish. I would expect that in case of a malloc() failure varnish fails back to streaming, and trash the dirty cache. Or break the TCP connection, and do a reset so the client get an error message on the lower level and can handle = it (retry). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-223065-13-DrlBPo4Qwx>