Again, thanks.
1) When I restart all the nodes in my cluster, I don't see my previous configuration come back, which is why I was wondering about the persistence. The was a restart them is by running /etc/init.d/openais stop on both nodes, then running /etc/init.d/openais start on both nodes. When the DC is finally elected..there are no resources configured... -Frank ________________________________ From: hj lee [mailto:kerd...@gmail.com] Sent: Wednesday, November 18, 2009 4:57 PM To: pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] getting started On Wed, Nov 18, 2009 at 2:27 PM, Frank DiMeo <frank.di...@bigbandnet.com> wrote: Thanks for you response, some comments: 1) So, if we cannot load a persistent configuration after a restart of the all nodes in the cluster, how does one automatically configure an (rebooted) unattended cluster with a known set of resources? Is it expected that a person will reconfigure a cluster if it were to all nodes in the cluster were to reboot? You don't have to reload it. The cluster configuration is saved in /var/lib/heartbeat/crm/crm-xx.raw and it survives across reboot. 2) If I'm trying to reduce the DC election time during a complete cluster reboot, so how can I load the dc-deadtime before a DC is elected? When you configure a cluster initially, just set the dc-deadtime, it will be persistent. 3) Thanks, that's was the problem 4) I'm sure your method will work, but the syntax that I used is right out of the documentation for pacemaker (example 6.16 of Pacemaker 1.0, Configuration explained"), so I don't see what's wrong with it. Regardless, I'll use your method. Oh, well. That's why we are here to catch a bug! Thanks
_______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
