Well, i have some health checks which are not very lightweight (don't
ask, another story). So its better to reduce its number to bare minimum.
Actually it would be quite cool, if you can use variables in you
configuration. And moreover if you can change these vars at runtime, it
would be awesome. I there are environment variables, but yet I didn't
check if they are what I am looking for.
You could control check intervals (probably its better to already have
some state, if one of your backup haproxys takes over), so you could
make checks less frequent instead of turning them off altogether.
Another point I encounter frequently, I use the same server (IPs) in
multiple backends, this duplicates configuration.
SRV1_IP=192.168.0.1
CHECK_INTER=10000
backend foo
server service1 $SRV1_IP check inter $CHCECK_INTER
backend bar
server service2 $SRV1_IP check inter $CHCECK_INTER
On 16.12.2016 20:50, Neil - HAProxy List wrote:
Stephan,
I'm curious...
Why would you want the inactive loadbal not to check the services?
If you really really did want that you do something horrid like tell
keepalive to block with iptables access to the backends when it does not
own the service ip
but why? you healthchecks should be fairly lightweight?
Neil
On 16 Dec 2016 15:44, "Marco Corte" <[email protected]
<mailto:[email protected]>> wrote:
Hi!
I use keepalived for IP management.
I use Ansible on another host to deploy the configuration on the
haproxy nodes.
This setup gives me better control on the configuration: it is split
in several files on the Ansible host, but assembled to a single
config file on the nodes.
This gives also the opportunity to deploy the configuration on one
node only.
On the Ansible host, the configuration changes are tracked with git.
I also considered an automatic replication of the config, between
the nodes but... I did not like the idea.
.marcoc
