On Wed, Jul 15, 2015 at 8:28 AM, Marco Corte <[email protected]> wrote: > Il 14/07/2015 22:11, Baptiste ha scritto: >> >> - when parsing the configuration, HAProxy uses libc functions and >>> >>> resolvers provided by the operating system => if the server can't be >>> resolved at this step, then HAProxy can't start > > [...] >> First, we want to fix the error when HAProxy fails starting up because >> the resolvers pointed by the system can't resolve a server's IP >> address (but HAProxy resolvers could). >> The idea here would to create a new flag on the server to tell HAProxy >> which IP to use. The server would be enabled when the IP has been >> provided by the expected tool. > >
Hi Marco, > Why not providing an option to start haproxy even if not all servers can be > resolved? That's the purpose of my mail. I need this feature, but I want to make it in a way which would satisfy the community. > Your proposal of the "init-addr" could be useful for a trick: I can set a > surely unreacheable address to let haproxy start and then force/wait for the > name resolution to have a working server. That's what we want. The hidden feature, is that you can start large farms and simply turn on DNS when spawning new application servers. Scale up without reloading HAProxy ;) > A "NX" server state would be very nice. noted, thx Baptiste
