@Markvr wrote:
From reading https://cbonte.github.io/haproxy-dconv/1.8/management.html#4 , when haproxy reloads, a new process is created and binds to the same port as the old one. Then when all connections to the old one have ended, the old process dies.
My question is: during this period when both processes are alive, can new connections go to the old process? There is nothing on the page linked above that explicitly says new connections can't be handled by the old process, but it would seem odd if this was possible. However I'm seeing issues where this appears to be occurring. This causes errors for these new connections because in my situation, the old process no longer has valid backends.
I'm using haproxy inside a Docker container is that is relevant.
haproxy: 1.6.6
kernel: 3.10.0-514.el7.x86_64
docker: 17.03.0-ce
Posts: 3
Participants: 3