Patrick, this is awesome. Here are my numbers: [root@server1 ~]# cat /proc/cluster/config/cman/hello_timer 5 [root@server1 ~]# cat /proc/cluster/config/cman/deadnode_timeout 21 [root@server1 ~]# I'm assuming these are seconds. I think if I increase the deadnode_timeout to maybe 120, then a network hiccup or major glitch (like a reboot of a switch) could be ignored. Thanks again! Jeff -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Patrick Caulfield Sent: Tuesday, January 17, 2006 7:58 AM To: linux clustering Subject: Re: Network hiccup + power-fencing = both nodes godown (redhat cluster 4) Jeff Harr wrote: > I thought about a crossover cable :) But I think that, these being > blade servers, there's no connection in the back for that. I could be > wrong though - I just don't have the hardware around to look at right > this second (its in a datacenter). > > One thing on the heartbeats: the message log says "missed too many > heartbeats". Off-hand, do you know where the number of heartbeats is > configured? /proc/cluster/config/cman/hello_timer /proc/cluster/config/cman/deadnode_timeout -- patrick -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
