On 8/10/07, Andreas Kurz <[EMAIL PROTECTED]> wrote: > On 8/10/07, Andrew Beekhof <[EMAIL PROTECTED]> wrote: > > On 8/9/07, Andreas Kurz <[EMAIL PROTECTED]> wrote: > > > On 8/8/07, Dejan Muhamedagic <[EMAIL PROTECTED]> wrote: > > > > On Wed, Aug 08, 2007 at 01:07:19PM +0200, Andreas Kurz wrote: > > > > > Hello all, > > > > > > > > > > I am running a two-node test cluster (heartbeat 2.1.2) using pingd as > > > > > an OCF resource and encountered the following behaviour in my > > > > > configuration: > > > > > > > > > > - I disabled clusterwide resource monitoring to restart heartbeat on > > > > > on one node, because lrmd was not working as expected > > > > > > > > What was it doing? > > > > > > I know what it was not doing ... executing monitors and monitor action > > > initiated by the DC (after an 'crm_resource -P') timed out. > > > > > > > - when the first node was up again and integrated again in the cluster > > > > > I reenabled clusterwide resource monitoring > > > > > > > > What do you mean by "clusterwide resource monitoring"? > > > > > > setting 'is-managed-default' in the crm_config section > > > > that setting only means that it can start/stop resources - it doesn't > > imply any monitoring > > Aaah ... I see, ok ... but the effect is the same, heartbeat does not > start or stop the resources. Why does the monitoring still continue > .... or is it suspended once an monitoring error is detected that > would cause stop/start events?
given: rscA (managed) rscB (unmanaged) rscA depends on rscB it is better to know if rscB fails and that rscA should be stopped than to let rscA fail(which has consequences if rscB ever becomes available again) > > > I am talking about the behaviour of the CRM when 'is-managed-default' > > > is reenabled again in a cluster and pingd is not running everywhere > > > and there are some nodes which have a pingd node attribute and some > > > which have not. As the pingd resource is a resource that influences > > > the score of nodes when placing other resources I think it would be > > > nice to have pingd started on all nodes _before_ all other resources > > > .... when there are constraints including pingd score_attributes. > > > > the pingd page describes two methods of starting it. > > to do what you describe, just use the ha.cf/respawn method > > Hmm, yes that would be better in such a situation. I only preferred > the pingd-clone because then the pingd attributes could be changed > dynamically .... is it possible to let heartbeart reread the ha.cf > file without a restart? If not, are ther plans to support it in the > near future? i dont know _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
