On Mon, 2009-05-25 at 15:26 +0100, John Bourke wrote: > Folks, > > Keepalived does not seem to have a mechanism to failover on the failure of a > process on the system. It has a load balancer which can select where > traffic is sent to based on a HTTP check or a script return code. But that > is for server selection in load balancing. It does in the latest versions, you can now add periodically run check scripts that can be used to determine a FAULT state. > One thing you really need to consider is flip flopping. If you have Node A > which is master, and when it goes down, Node B becomes master, the when node > A comes up again it will become master. A mechanism to "stick to the node > last used" would be better so that a master with an intermittent failure > does not cause flip flops. You can do that with keepalived as well, check out the preemption control parameters (noprempt etc.) > Thanks > > John -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
