Greetings,
The first place I'd start looking would be the timings in the HAProxy
logs to see what part of the process is being slow.
In the logs (if http mode) the default format has five timing values in
the column after the backend_name/server_name component which will say
what part of the request is taking too long.
Scroll down on
https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#8.2.3 a
bit for the definitions of the various values.
If your in TCP log mode for the connections in question you will only
have three of said timings instead of six, but still the place to start
I think.
If you paste some examples here I might be able to spot something in the
timing or help with figuring out what they mean if its not clear.
- Chad
On 03/09/2016 08:26 AM, matt wrote:
Hi guys. I been using HAproxy for two years now, and I really love the product.
Simple, quick and really well documented.
Lately I been having an issue that keeps me awake by night,
and maybe you could help me solving.
I have 4 VM's behind 2 HA proxies. On every VM I have a Docker
container serving on port 80.
So far is running great, but lately im having issues on deployments.
The deployment scenario is like this:
I go through every VM (one at the time),
remove the VM from both LB's with socat, stop the container
and then create a new container.
The thing is, just when I delete the container (not when I
remove from the LB), the response time of the OTHERS VM's
starts increasing, which causes my deploys to
have a peak in response time.
The way I have to test the response times is a app that
keeps pinging the app from the outside and see the response
payload to see which server is it, which lead me to two ideas
1) The apps on the others VM's gets overloaded
with the traffic (which I don't believe is the case, because
I've tried using 1 more VM and the issue remains
the same)
2) HAproxy is rerouting some request in a way that causes slowness
Does this sound familiar to any of you?
How can I debug this kind of events?
Thanks in advance
