On 2/28/12 5:27 PM, Andrew Beekhof wrote: > On Wed, Feb 29, 2012 at 5:21 AM, William Seligman > <[email protected]> wrote:
>> While I was setting up the test for the previous paragraph, there was a >> problem >> with another resource (ocf:heartbeat:exportfs) that couldn't be properly >> monitored on either node. This led to a cycle of fencing where each node >> would >> successively fence the other because the exportfs resource couldn't run on >> either node. I had to quickly change my configuration to turn off monitoring >> on >> the resource. > > Not being able to run is fine, but not being able to stop would > definitely cause fencing. > Make sure the RA can always stop ;-) I'm not the one who wrote ocf:heartbeat:exportfs. I've already had my fling with trying to revise it. I can only hope that the folks who wrote it knew what they were doing; they certainly know more than I do! -- Bill Seligman | Phone: (914) 591-2823 Nevis Labs, Columbia Univ | mailto://[email protected] PO Box 137 | Irvington NY 10533 USA | http://www.nevis.columbia.edu/~seligman/
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
