On 13/10/2017 10:32 πμ, Joel W Kall wrote: > We're using HAProxy 1.6.3 to load balance and route HTTP traffic to hundreds > of backend servers. We > reload the config often (several times a day), both automatically when a > server fails and manually > for administrative reasons. > > The problem is that running the reload command takes 3 minutes on one of our > HAProxy servers (Ubuntu > server 16.04). It does not seem to matter whether the server has traffic or > not. On our other > servers with the same version of OS and HAProxy, the reload takes 1-5 > seconds, regardless of load. > We have a bunch of long-running requests but as I said it does not seem to > matter if the server has > traffic or not. > > We can see that a new process is spawned, but then it takes a few minutes > before it starts accepting > traffic (or at least until the CPU usage of the new process climbs above 0% > and the it emits log > messages about starting backends). >
Without seeing the conf, it is quite difficult to get a proper advice. Loading SSL certificates can take some time, how many do you have? > Questions: > > - What can cause HAProxy to take so long to reload? > Does the issue occur only on restart? If not then start haproxy with strace -ttt -T and see where it spends most of the time > - How can we find out what it's doing? For instance, what level of logging do > we need to enable and > what would we look for in the log? > Use strace as I mentioned. > - Do you have a suggestion for a fix? > We can only provide a fix even we know the root cause of the problem and right now we don't know what is causing the problem. Cheers, Pavlos
signature.asc
Description: OpenPGP digital signature
