Re: stale arp after master/master ?

* Alexandre Cassen

> Please elaborate, I can fix quickly ! (to be honnest I just didnt get
> time since last release to look deeply into bug report).

No problem, I didn't want to nag you either.

In any case, I think my original messages was pretty clear.

1) reload+virtual_routes causes a segfault which in turn leads to a
perpetual multi-master "split brain" service impacting situation,
details here:

http://thread.gmane.org/gmane.linux.keepalived.devel/4465

2) reload+preempt_delay causes a similar split-brain situation lasting
for the duration of preempt_delay, as the node sits there with its VIPs
active without sending hellos, details here:

http://thread.gmane.org/gmane.linux.keepalived.devel/4466

These bugs were individually serious enough for me to have to freeze the
configuration until the next maintenance window, where I could downgrade
to the distro-provided version (1.2.2 in Ubuntu LTS). While I would have
liked some of the new features in later versions, especially IPv6
improvements, stability is more important.

So please look through my messages from last month, and if something is
still unclear and needs elaboration on, then let me know what and I'll
do my best. :-)

> I will fix this preempt issue introducing a new keyword instead of
> changing default behaviour, but what are the others issues ? I will have
> a look at github tracker...

I'd say that the old meaning of preempt_delay was the one you'd
intuitively expect, and it also matched the documentation. That can't be
said for the current behaviour. Since the distros aren't shipping the
changed meaning yet I would recommend reverting the patch and adding the
new functionality with a new keyword, so that people's configurations
doesn't need to change when the keepalived package gets upgraded. Anyway
I elaborated a bit on this in my original message too.

I didn't file github issues, but if you want me to I'll be happy to do
so. Just let me know.

Tore


------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees