Hello, On 02/08/2012 08:32 PM, James FLatten wrote: > Maybe someone can help me understand this behavior. I have a two node > cluster built using the "Cluster from Scratch" document. I am testing > various behaviors, one of which is to bring up the cluster services on > one node while it's partner node is offline. > > What I am seeing is this: > > I start up Corosync and pacemaker one the first node. The system waits > dc-deadtime (correct?) and then successfully fences the other node. At > this point I would assume that it would bring up the resources, but what > I find is that the system waits until the first cluster-recheck-interval > (15min) pops and then starts the resources. > > Is this correct behavior? And if so, can I adjust the > cluster-recheck-interval so my services come online quicker?
No, this is not a correct behavior ... but for more ... not enough information. Are you using latest Pacemaker? What does your complete config look like? What's your DRBD version (if in use)? Logs from the time of cluster start until resource startup? Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now > > Thank you, > Davin > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org