On Thu, 2008-04-17 at 18:10 +0100, gordan@xxxxxxxxxx wrote: > On Thu, 17 Apr 2008, Harri.Paivaniemi@xxxxxxxxxxxxxxx wrote: > > > If you just want to have a cluster where client network can be down > > infinitely without cluster to take actions, > > you have to run cluster heartbeat via cross-cable and deny cluster's > > link monitoring in client interface. > > > > Or then start using qdisk and build heuristics. > > At that rate you might as well just not bother specifying a fencing device > - the whole cluster will just lock up until the network comes back and it > can re-connect and re-establish quorum. > > > Note, that in RHCS 5 deadnode_timeout doesn't exist anymore in /proc. > > It's totem token there, but havn't checked where it lives in /proc or > > maby it's in /sys nowadays. > > Thanks for that. :-) It's just cluster.conf at this point. <totem token="X"/> It's not possible to specify different timeouts on different nodes as you can with deadnode_timeout. Of course, I think doing different deadnode_timeouts is kind of nuts :D -- Lon -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
