Hey All,
We have UCARP and HAproxy configured and setup between two servers.
HAproxy is bound to the UCARP VIP between the nodes. There are four
services per hoer: four on SRV1 (primary) and same four apps on SRV2
(secondary) We need active / passive behavior, since apps don't support
an active / active config. We have one UCARP VIP for each application.
SRV1 primary
SRV2 secondary
We need all four VIP's and HAproxy processes to failover to the standby if:
1) One of the four processes on the primary fails.
2) Primary host fails ( This piece is easier. )
When all fail over to the standby, we need them capable of failover back
if the secondary (standby) fails in the future.
We can't seem to have all of them stick on the standby (now primary)
when the primary comes back up or even when the one failed service comes
back on SRV1 (former primary).
They end up flipping back and we end up in a situation where some of the
traffic goes to SRV1 and some to SRV2.
We tried the:
stick-table type ip size 1 nopurge peers LB
stick on dst
As well as rise 9999999
but those eventually fail over. Wanted to know what is the best
practice in this case?
Second question we have is how to split up HAproxy processes into
separate start and stop scripts? Currently we stop and start using only
the main restart script /etc/init.d/haproxy but that stops all or starts
all. Has anyone split these up into separate start stop scripts to
control individual HAproxy instances? In other environments we find
that they start multiple copies of the same HAproxy definition. We need
better fine grained control of each one.
--
Cheers,
Tom K.
-------------------------------------------------------------------------------------
Living on earth is expensive, but it includes a free trip around the sun.
