scripts and Heartbeat.
alanr at unix.sh
Fri Feb 8 19:41:33 MST 2002
Michael Cunningham wrote:
> I have the latest heartbeat running between two LVS directors.
> It is working great. It can fail back and forth without
> Now I would like to setup LVS connection state synchronization
> between the two LVS directors. But I am two problems/questions.
> Can I run the multicast connection sync over my 100 mbit
> private lan link which is being used by heartbeat without
> causing problems? Shouldnt be to much bandwidth.
Heartbeat uses negligible bandwidth. If you want to know if you have a
problem, then set deadtime up to something high, and set warntime to the
time you want to set deadtime to, and then load thing up as high as you can
get them. If any heartbeat packets come in over "warntime", then you'll get
warnings in the logs.
> How can I setup heartbeat to always run..
> ipvsadm --start-daemon=master --mcast-interface=eth1
> on the current master.. and
> ipvsadm --start-daemon=backup --mcast-interface=eth1
> on the current slave at all times?
> The master can run a script when it starts up/obtains/gives resources
> but I don't see anyway for the slave to run a script when it
> starts up.
There are three states a machine can be in.
3) neither (before heartbeat starts)
If it is acceptable to run the slave code before heartbeat starts, then you
can just start it in an init script before heartbeat runs, and then change
your resource script to run the slave script whenever it gives up the
resource, and run the master script when it takes over as master.
Does this help?
-- Alan Robertson
alanr at unix.sh
More information about the Linux-HA