Hi, On Mon, Dec 14, 2009 at 11:08:26AM +0100, Tobias Appel wrote: > Hi, > > I'm still running Heartbeat 2 and according to this site: > http://www.linux-ha.org/ciblint/crm_config > > the option means the following: > > is-managed-default [boolean: default=true]: Should the cluster > start/stop resources as required > Should the cluster start/stop resources as required > > Can someone please elaborate this? The problem I'm facing now in my
If set to false, cluster won't manage resources, i.e. it won't start/stop them. That's what you want in case you're upgrading software for a resource. > 2-node cluster is the following: > > - One Node dies and get's STONITH'd (poweroff) > - the Node gets powered on by us and joins the cluster again > - Heartbeat stops all resources on the current node and starts them up > on the newly joined node You can use resource-stickiness to keep resources on a node where they're already running. But that's a policy change. > This is very inconvenient for us, as we have a short outage and also the > DRBD disc is not yet synchronized on the failed node, so we run into > trouble sometimes. Perhaps not to start heartbeat on boot? > Can I stop this behaviour using the option mentioned above? No. That would effectively make your cluster useless. Thanks, Dejan > Thanks in advance, > > Tobi > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
