[Pacemaker] STONITH Deathmatch Explained

Lars Marowsky-Bree lmb at suse.de
Tue Aug 11 13:39:24 UTC 2009


On 2009-08-11T00:41:42, Tim Serong <tim at wirejunkie.com> wrote:

Hi Tim,

it's worth noting that we hunted down an additional new scenario which
could cause this to trigger.

Some switches seem to take noticably longer to get multicast
communication up, while unicast or even broadcast are already
operational. So despite being able to ping, OpenAIS can't see the other
side and goes into this fencing loop.

This can, of course, be avoided by setting stonith-action=poweroff or
disabling OpenAIS from being started at boot, but the best fix is to fix
the switches. ;-)

heartbeat had an "initdead" parameter for the very first initial
wait time to pronounce the other side dead. Maybe something similar
would become OpenAIS as well.


Regards,
    Lars

-- 
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde





More information about the Pacemaker mailing list