My company is evaluating ASL HA for use to learn the ins and outs of the current functionality before putting it into production.
Some notes we had with #1 and #2 being a significant disappointment for us:
1. If you are using Serial + Ethernet for HA, if one is disconnected you don't get any notification of it until the other connection goes down. Which basically defeats the purpose of using both Serial + Ethernet since you won't know about the failure until the other one fails and then you end up with both instances running at the same time. Anyone else see this as a problem?
We opened a ticket with Astaro who basically danced around the issue and said HA is being revamped for V7. Unfortunately, this still leaves us with a less than optimal siutation until possibly V7 is released and then who knows if V7 will even address the issue? (See these 2 threads for 2 outstanding issues we have handled the same way: #1 #2)
2. HA transfer is very very slow. It takes 25-45 seconds to perform a failover even for a planned outage like an up2date, so I'd hardly call it HA if you are looking for good uptime even for planned updates and reboots. More like warm standby. Each update which requires a reboot requires 2 reboots (update master, failover to slave for master reboot, failover to upgraded master after reboot) so that means you get 40-90 seconds of downtime even with HA.
3. NIC link failures which trigger a failover result in the master being shutdown. Unexpected, but OK.
4. There's no way to manually failover to a "preferred" HA instance short of rebooting the current master or pulling a cable if it isn't the one you want to be running. Would be nice to have a button to manually trigger a failover.
5. Any changes to the HA configuration need to be followed by a system reboot.
I think that's it for now. Hope this helps anyone who is thinking about trying an Astaro HA setup.
This thread was automatically locked due to age.