thanks, but where do I have to put the timeout?
Inside fence seciotn of the nodes:
<fence>
<method name="1">
<device name="ilonode01"/>
</method>
</fence>
or inside definition of fence devices:
<fencedevices>
<fencedevice agent="fence_ilo" hostname="10.4.192.208"
login="fenceuser" name="ilonode01" passwd="rhelclasi"/>
<fencedevice agent="fence_ilo" hostname="10.4.192.209"
login="fenceuser" name="ilonode02" passwd="rhelclasi"/>
</fencedevices>
?
It is frustrating to be always impossible to check syntax and
parameters for this cluster.conf mistery file... ;-(
Thanks
Gianluca
On Tue, Feb 24, 2009 at 4:01 PM, Marc Grimme <grimme@xxxxxxx> wrote:
> We've solved this problem by using fence_timeouts that are dependent on the
> nodeid. Means node0 gets timeout=0 and node1 gets timeout=10. Then node0 will
> always survive. That's not the optimum way but works.
> Or use qdiskd and let it detect the networkpartitioning (whereever it happens)
> and decide which side should survive by a heuristic.
> Marc.
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
