Running heartbeat 2.0.8 I have a problem with unnecessary moving of our resource to a different node when a pingd node goes dead or comes back up. I am talking about the ping node itself going dead, so ALL cluster nodes lose connectivity to it. There seems to be a race condition depending on which node detects and reports the ping node status change first. If the node which is not running the resource reports the status change first, then temporarily the ping score is unbalanced and the resource is moved. It seems to me there should be some way of configuring some sort of cluster delay between getting a ping node status change and moving resources to another node.
Thanks, Brad _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
