Hi,
I'm running haproxy in ec2 environment - and there is one problem I noticed.
The backend servers are configured as names and not ip - if backend
server IP changes
and even if the /etc/hosts on haproxy server is updated - haproxy does
not catch this change.
It has to be restarted to catch this change - now is there builtin
haproxy configuration work around for this?
I can think of many ugly & unreliable workarounds - but the most natural
seems to be - if haproxy backend healthcheck
is failing (or more specifically it fails to connect to backend) it
should try to check if the backend ip has changed with getnameinfo and
update it if needed
before each healtcheck. This way there is no need to reload/restart
haproxy by external tools - as well statistics will not be lost.
Is there chance for this feature to be implemented?
Thanks
Alex
