On Fri, 23 Aug 2024 at 18:55, BJ Taylor <b...@greenseedtech.com> wrote:
>
> We are trying to deploy HAProxy into our environment. We have a script that
> does some 600k api calls during approximately 24 hours.
How many concurrent connections / transactions though?
> During that time, when haproxy is in place, there are a handful (8-12) of
> responses that come back as 502 with SH--.
As per the documentation:
SH The server aborted before sending its full HTTP response headers, or
it crashed while processing the request. Since a server aborting at
this moment is very rare, it would be wise to inspect its logs to
control whether it crashed and why. The logged request may indicate a
small set of faulty requests, demonstrating bugs in the application.
Sometimes this might also be caused by an IDS killing the connection
between HAProxy and the server.
You should disable custom format logging, enable httplog format and
share the affected SH log line.
> tune.bufsize 8388608
> tune.maxrewrite 1024
bufsize should usually be 16K maybe 32K for some specific application
requiring huge headers, but not 8M. I think 8M is unreasonable and I
think it will lead to issues one way or another.
> timeout connect 86400s
> timeout client 86400s
> timeout server 86400s
1 day long timeouts will probably also lead to an issue at some point,
due to sessions not expiring.
Lukas
