Andreas Mock wrote: >> -----Ursprüngliche Nachricht----- >> Von: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] Im Auftrag von >> Bryan Manzeck >> Gesendet: Dienstag, 11. März 2008 16:58 >> An: [email protected] >> Betreff: [Linux-HA] Node fences itself? > > Hi Bryan, > >> Hello, >> I have STONITH setup with HP iLO cards and I am wondering if >> the clone resource should run on itself? What I am trying to >> ask is if a node should be able to fence itself? Is there a >> best practice for this? > > Ha...that's a good question. We had some discussion about that > on the list. I really don't know the current status. So be careful > what I say: > > a) Dejan says that there is code in the stonithd to prevent a node > to shoot itself. BUT: I had a test case where exactly this happened. > I don't know what is really true, now. > > b) What I do: I have single primitive stonith resources for every > node I want to shoot. Every primitiv has a location constraint giving > the node which has to be shot by exactly this stonith resource a > big penalty, but NOT -INFINITY. > > c) Why the penalty: > 1) I want to run the stonith resource on any node BUT the node to stonith. > 2) In a two node scenario. As soon as one node dies the stonith resource > is moved to the last goo node. As soon as self stonithing is working, this > should be a valid layout.
Hi Andreas, I've been having trouble w/ my (riloe) stonith resources in my 2 node cluster in testing. If I pull the cable of the public interface on node A, the ilo resource allowing node A to shoot node B stops and doesn't recover when the connection is restored. I'm using -infiniti, i'll change that to -2000 or something. The stonith resource should move to node B if the connection goes down and move back to node A when the connection is restored. I'll test that. Thanks for your comments! regards, Johan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
