Look at varnishlog, and find the error in the log. And possibly look at a
few BeReq before that.

I've seen apache wrongly replying 304 with body. As Varnish expect no body,
it bytes are read as the next request's headers, and as you can guess, that
doesn't work well. You may be affected my a variant of that.

On Sep 21, 2016 11:14, "Tobias Honacker" <t.honac...@googlemail.com> wrote:

> Hi all,
>
> we are facing some issues trying to stresstest our oAuth App using Varnish
> 4.0.3 and Gatling
>
> Infra:
>
> LB -> Apache (SSL Offloading) + Varnish -> Appserver (Apache + Tomcat)
>
> Varnishlog:
> http://pastebin.com/tCWgi01H
>
> VCL:
> http://pastebin.com/cEdzAwxs
>
> tcpdump on our app server with 1 req/s (varnishlog 200):
> http://pastebin.com/XFVsANiN
>
> tcpdump on our app server with >= 2 req/s (varnishlog 503er):
> http://pastebin.com/f2EKADpx
>
> If varnish throws HTTP 503 the connection: close header is missing
>
> Running tests using pipe works fine, because pipe sets connection: close
> Running tests without varnish works fine, too.
>
> The Apaches using KeepAlive:
>
> KeepAlive On
> MaxKeepAliveRequests 100
> KeepAliveTimeout 10
>
>
> Any suggestions?
>
> Thanks in advance and best regards
> Tobias
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc@varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
_______________________________________________
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

Reply via email to