On Mon, 2008-01-14 at 16:01 -0500, Scott McClanahan wrote:
> Thanks for the response but I think the easiest and best approach for me
> would simply be to mod the config with the appropriate weight (this
> doesn't happen so frequently that it's a burden) and perform a reload.
> I just need to be sure keepalived handles a HUP signal as I'd expect. I
> noticed in previous releases HUP signals weren't always handled so
> gracefully. I'd like to make sure the master stays master and
> interruptions to users are avoided.
I believe this is a function of the length of the config, any changes
that need to be made and your VRRP advert interval (and probably
ancillary things like disk IO). If a HUP makes keepalived take longer
than necessary to re-read and do $stuff, it'll stop sending adverts and
you may experience a race failover while the master fiddles with config
(and Rome burns).
You may (although I hesitate to say this if keepalived is well-used by
you) want to switch to ldirectord, since it does in-service config
changes (like weights) without a signal. As long, of course, as the
config is sane!