2008/6/4 Alexander Hofmann <[EMAIL PROTECTED]>: > Andrew Beekhof wrote: >> >> On Wed, Jun 4, 2008 at 8:18 AM, Alexander Hofmann >> <[EMAIL PROTECTED]> wrote: >> >>> >>> Hello list, >>> >>> I have a problem with my Heartbeat and STONITH configuration: >>> When I disconnect the two private links both nodes are STONITHed. >>> >> >> Right - because neither side can see the other. >> And because the cluster only has two nodes, both sides also have >> quorum (which allows them to shoot the other). >> >> Two options: >> - add a third node (so only one side of the cluster will have quorum) >> - set the "stonith-action" option to "poweroff" (which would prevent >> the shot node from shooting the survivor when it returns) >> >> > > Hi, > > thank you for your fast reply. > > stonith-action ist already set to "poweroff". > I've just tried to set ilo_powerdown_method to "power" and as a result > _both_ nodes do a normal shutdown... > > Any ideas aside from a third node?
What else you can do if you lose connection with your peer but everything else's just fine. ;) If there is a pingable node. I used to put stonith with a pingd resource, which updates in a rather high frequency. Then pingd will then detect the lost before heartbeat, and stop the stonith resource accordingly. It's tricky cause sometimes you may need different pingd instance for different purpose. Of course, it'll be far better to have ping/disk/blahblah based quorum plugin in the future. ;) > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
