On Fri, Aug 05, 2011 at 11:17:16AM +0300, Piavlo wrote: > But why do a reload of haproxy in other situations (much more common in > my use case and loose statistics and possibly some connections) if there > could be a config option that tells haproxy to re-resolve name to ip - > then backend health check fails?
It's not a matter of config option. You're supposed to run haproxy inside a chroot. It will then not have access to the resolver. I could ask the question the other direction : why try to resolve a name to IP when a check fails, there is no reason why a server would have its address changed without the admin being responsible for it. Also, in your case it would not fix the issue : resolving when the server goes down will bring you the old address, and only after caches expires it would bring the new one. In the mean time, someone else might have got the old address before you have a new one, so this means that it is still possible that only the old address is used. There is no way to reach a reliable behaviour with unreliable configuration processes. Regards, Willy
