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 - "/etc/init.d/hearbeat stop" hanged infinitely so I killed all heartbeatprocesses and the second node stonithed the other as expected, the resources were not started on the second node because they were unmanaged - when the first node was up again and integrated again in the cluster I reenabled clusterwide resource monitoring - now the resources were all started on the second node, whith its higher weight because of the already running pingd and its score_attributes Now my question is: Is it possible to configure heartbeat to always wait for all pingd clone-instances to be started before the calculation of the scores for other resources (where a constraint with a pingd score_attribute exists) ? The only idea I had was to start pingd from ha.cf or to stop pingd also on the second node before reenabling the resource monitoring to allow a "clean" resource placing. Regards, Andreas
pe-input-8.bz2
Description: BZip2 compressed data
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
