Hi, On Fri, Nov 19, 2010 at 02:01:12PM -0700, Greg Woods wrote: > On Fri, 2010-11-19 at 10:51 +0100, Sébastien Prud'homme wrote: > > > for simulating that problem, i set meatware with the highest priority, > > meatware is always supposed to be the LOWEST priority. It is only used > if no other STONITH device is available. meatware also is designed to > wait an unknown amount of time for human intervention; I'm not sure it > will ever time out.
Yes it does time out just like any other resource. The timeout is specified with stonith-timeout instance parameter or cluster property. Thanks, Dejan > What happens if you do the reverse: set riloe with the higher priority, > but intentionally create a problem where riloe won't work? Will it fall > back to meatware then? > > This is what I do. I don't know anything about riloe, I use ipmilan, but > I have created a failure of the communications link between the two > nodes so that ipmilan will fail, then it falls back to meatware and I > can at least get one node to take over all the resources manually if the > internal communication between them fails. > > --Greg > > > _______________________________________________ > 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
