out of workspace (bo)

[Dridi Boukelmoune]

Hi Kevyn,

On Wed, Aug 30, 2023 at 11:37 AM Kevyn Fyleyssant
<kevyn.fyleyssant at gmail.com> wrote:
>
> Here is my VCL :
> https://pastebin.com/TpN8r0Um
>
> And my varnishd command :
> /usr/sbin/varnishd -a :8181 -p feature=+http2 -p http_resp_hdr_len=200k -p http_resp_size=2M -p http_req_hdr_len=200k -p workspace_backend=256k -p workspace_client=256k -p http_max_hdr=256 -f /etc/varnish/default.vcl -s malloc,4G

You already have a fairly large workspace, but to solve this you will
need to further increase workspace_backend.

You configured Varnish to accept up to 200kB per header field, and up
to 2MB per response headers (all fields combined). The worst case
scenario wouldn't fit in 256kB. The file size should have no
significant effect on workspace consumption, so this recurring
overflow is probably caused by beresp headers alone.

You should first make sure you have a good understanding of the origin
server and why it may produce such large response headers.

If this is legitimate, there is no way around increasing
workspace_backend. Your VCL isn't doing workspace-intensive
operations, so a little over 2MB (for example 2MB+64kB aka 2102kB)
should be enough.

Dridi